CVE-2025-38212

Published Jul 4, 2025

Last updated 3 months ago

Overview

Description
In the Linux kernel, the following vulnerability has been resolved: ipc: fix to protect IPCS lookups using RCU syzbot reported that it discovered a use-after-free vulnerability, [0] [0]: https://lore.kernel.org/all/67af13f8.050a0220.21dd3.0038.GAE@google.com/ idr_for_each() is protected by rwsem, but this is not enough. If it is not protected by RCU read-critical region, when idr_for_each() calls radix_tree_node_free() through call_rcu() to free the radix_tree_node structure, the node will be freed immediately, and when reading the next node in radix_tree_for_each_slot(), the already freed memory may be read. Therefore, we need to add code to make sure that idr_for_each() is protected within the RCU read-critical region when we call it in shm_destroy_orphaned().
Source
416baaa9-dc9f-4396-8d5f-8c081fb06d67
NVD status
Modified
Products
linux_kernel, debian_linux

Risk scores

CVSS 3.1

Type
Primary
Base score
7.8
Impact score
5.9
Exploitability score
1.8
Vector string
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Severity
HIGH

Weaknesses

nvd@nist.gov
CWE-416

Social media

Hype score
Not currently trending
  1. 🚨 CRITICAL: #SUSE releases kernel security patch SUSE-SU-2025:03222-1. Fixes 4 CVEs, including CVE-2025-38001 & CVE-2025-38212 (CVSS 8.5). Impacts SLE 15 SP6/SP7 & openSUSE Leap 15.6. Read more:👉 https://t.co/NozG7Yo3tN #Security https://t.co/Fkp5gTQbFk

    @Cezar_H_Linux

    16 Sept 2025

    5 Impressions

    0 Retweets

    0 Likes

    0 Bookmarks

    0 Replies

    0 Quotes

  2. URGENT: Patch #SUSE Linux NOW. Live Patch 24 (SUSE-SU-2025:03194-1) fixes 7 vulnerabilities, including CVE-2025-38212 (CVSS 8.5). Affects SLE 15 SP5, openSUSE Leap 15.5. Risks: Privilege escalation, DoS. Read more:👉 https://t.co/bmF6dWLSFt #Security https://t.co/a6UaQ3a9PE

    @Cezar_H_Linux

    15 Sept 2025

    54 Impressions

    0 Retweets

    0 Likes

    0 Bookmarks

    0 Replies

    0 Quotes

  3. 🚨 CRITICAL ALERT for @SUSELinux & @openSUSE users! Live Patch 17 for SLE 15 SP5/Leap 15.5 patches 9 vulnerabilities, including 2x CVSS 8.5 flaws (CVE-2025-38212, CVE-2025-38001). Read more:👉 https://t.co/YcyQobEZDQ #LinuxSecurity #CyberSecurity #SUSE https://t.co/khI04

    @Cezar_H_Linux

    14 Sept 2025

    41 Impressions

    0 Retweets

    1 Like

    0 Bookmarks

    0 Replies

    0 Quotes

  4. URGENT: Patch #SUSE Linux NOW. Live Patch 17 for SLE 15 SP5 fixes 9 critical kernel vulnerabilities (CVE-2025-38212, CVE-2025-38001, etc.). Risk: Local Privilege Escalation & DoS. Read more:👉 https://t.co/qZMhtWMRT4 https://t.co/f532a39oB0

    @Cezar_H_Linux

    14 Sept 2025

    83 Impressions

    0 Retweets

    0 Likes

    0 Bookmarks

    0 Replies

    0 Quotes

  5. 🚨 Critical #Linux kernel update for #SUSE 15 SP5 & #openSUSE Leap 15.5! Patch CVE-2025-21701 (CVSS 7.0) and CVE-2025-38212 (CVSS 8.5) to prevent local privilege escalation and DoS. Read more: 👉 https://t.co/fBfEvRq7yN https://t.co/uN23RVswZG

    @Cezar_H_Linux

    14 Sept 2025

    79 Impressions

    0 Retweets

    0 Likes

    0 Bookmarks

    0 Replies

    0 Quotes

  6. 🚨 URGENT #Security Update for @SUSE Linux users! Live Patch 22 for SLE 15 SP5/ #openSUSE Leap 15.5 patches 7 critical kernel vulnerabilities. CVE-2025-38212 (CVSS 8.5) allows privilege escalation. Read more: 👉 https://t.co/I1DlWx37KK https://t.co/wjgmhLEu8J

    @Cezar_H_Linux

    14 Sept 2025

    80 Impressions

    0 Retweets

    1 Like

    0 Bookmarks

    0 Replies

    0 Quotes

  7. 🚨 Critical Linux Kernel Patch Alert! 🚨 #SUSE's Live Patch 40 for SLE 15 SP4 fixes 5 important CVEs, including CVE-2025-38212 (CVSS 8.5). Local privilege escalation & DoS risks. Affected products: Leap 15.4, SLES, SAP HANA, HPC, Micro. Read more: 👉 https://t.co/qc7YH

    @Cezar_H_Linux

    13 Sept 2025

    139 Impressions

    0 Retweets

    1 Like

    0 Bookmarks

    0 Replies

    0 Quotes

  8. 🔐 CRITICAL: #SUSE Linux Kernel Patch Alert! 🔐 CVE-2025-38212 (CVSS: 8.5) patched for SLE 15 SP4 & openSUSE Leap 15.4. Fixes a local privilege escalation vulnerability in IPCS. Read more:👉 https://t.co/ndHaZsNDwu #Security https://t.co/iiRuECbyx6

    @Cezar_H_Linux

    13 Sept 2025

    115 Impressions

    0 Retweets

    0 Likes

    0 Bookmarks

    0 Replies

    0 Quotes

  9. Urgent: #SUSE releases Live Patch 41 for Linux Kernel (SLE 15 SP4/Leap 15.4). Patches 4 vulnerabilities: CVE-2025-37890, CVE-2025-38000, CVE-2025-38001 (CVSS 8.5), CVE-2025-38212 (CVSS 8.5). Read more: 👉 https://t.co/L6VAeHng7B #Security https://t.co/FyoVgvjs8m

    @Cezar_H_Linux

    13 Sept 2025

    113 Impressions

    0 Retweets

    0 Likes

    0 Bookmarks

    0 Replies

    0 Quotes

  10. URGENT: #SUSE releases critical Linux kernel security patch for SLE 15 SP4 and #openSUSE Leap 15.4. Fixes 6 vulnerabilities, including: ✅ CVE-2025-38212 (CVSS 8.5) - IPC UAF ✅ CVE-2025-38001 (CVSS 8.5) - HFSC flaw Read more:👉 https://t.co/uqFzf8yqz1 https://t.co/

    @Cezar_H_Linux

    13 Sept 2025

    114 Impressions

    0 Retweets

    0 Likes

    0 Bookmarks

    0 Replies

    0 Quotes

  11. 🚨 Critical #SUSE Linux Kernel Patch Released! 🚨 Live Patch 29 (SUSE-SU-2025:03175-1) fixes 9 vulnerabilities. CVE-2025-38212 (CVSS 7.8): IPC flaw. Read more: 👉 https://t.co/Tgph25THii #Security https://t.co/ycvdYq3H5t

    @Cezar_H_Linux

    12 Sept 2025

    103 Impressions

    0 Retweets

    0 Likes

    0 Bookmarks

    0 Replies

    0 Quotes

  12. 🚨 Critical patch for #SUSE SLE 15 SP4 & #openSUSE Leap 15.4! Live Patch 31 fixes 9 kernel vulnerabilities, including high-severity CVEs: CVE-2025-38212 (CVSS 8.5). CVE-2025-38001 (CVSS 8.5) . Read more:👉 https://t.co/59ducSDAqD #Security https://t.co/NH2uNmjEHK

    @Cezar_H_Linux

    11 Sept 2025

    1 Impression

    0 Retweets

    0 Likes

    0 Bookmarks

    0 Replies

    0 Quotes

  13. URGENT: Patch your #SUSE Linux 15 SP7 systems now! New kernel vulnerability (CVE-2025-38212) patched. CVSS: 8.5. Allows local privilege escalation. Read more: 👉 https://t.co/pNNqYn2cvt #Security https://t.co/WXJJtPjrW8

    @Cezar_H_Linux

    10 Sept 2025

    62 Impressions

    0 Retweets

    0 Likes

    0 Bookmarks

    0 Replies

    0 Quotes

  14. URGENT: #SUSE patches 6 critical Linux Kernel vulnerabilities (SUSE-SU-2025:03109-1). CVSS Scores up to 8.5! Impacts: CVE-2025-38212 (IPC), CVE-2025-38001 (HFSC), and more. Read more: 👉 https://t.co/BnY4fxSrYJ #Security https://t.co/i2uifmu70P

    @Cezar_H_Linux

    10 Sept 2025

    64 Impressions

    0 Retweets

    0 Likes

    0 Bookmarks

    0 Replies

    0 Quotes

  15. 🚨 CRITICAL: #SUSE releases urgent kernel security update for SLE 15 SP6 (Live Patch 0). Patches 11 CVEs, including high-severity flaws: CVE-2025-38087 (UAF in net/sched) and CVE-2025-38212 (IPC flaw). Read more: 👉 https://t.co/fkbU7FavmN #Security https://t.co/75FBOResgR

    @Cezar_H_Linux

    10 Sept 2025

    18 Impressions

    0 Retweets

    0 Likes

    0 Bookmarks

    0 Replies

    0 Quotes

  16. URGENT: #SUSE patches 5 critical CVEs in Linux Kernel RT for SLE 15 SP7. CVE-2025-38212 (CVSS 8.5): IPC flaw CVE-2025-38001 (CVSS 8.5): HFSC flaw Read more: 👉 https://t.co/X16DdiVkST https://t.co/NIxAz9kbmc

    @Cezar_H_Linux

    10 Sept 2025

    60 Impressions

    0 Retweets

    1 Like

    0 Bookmarks

    0 Replies

    0 Quotes

  17. URGENT: Patch #SUSE Linux 15 SP6 now! 🚀 CVE-2025-38212 (CVSS: 8.5) allows local privilege escalation in the kernel. Read more: 👉 https://t.co/6V88FlDf45 #Security https://t.co/Boea0HGkKm

    @Cezar_H_Linux

    9 Sept 2025

    44 Impressions

    0 Retweets

    0 Likes

    0 Bookmarks

    0 Replies

    0 Quotes

  18. 🚨 Critical patch for #SUSE Linux Enterprise 15 SP6! CVE-2025-38212 (CVSS: 8.5) patches a local privilege escalation flaw in the kernel. Affects Server, SAP, and Real-Time systems. Read more: 👉 https://t.co/0k0Mn5G5aI #Security https://t.co/jNv8FB4WFe

    @Cezar_H_Linux

    9 Sept 2025

    42 Impressions

    0 Retweets

    0 Likes

    0 Bookmarks

    0 Replies

    0 Quotes

  19. 🔐 Critical patch for #SUSE SLE 15 SP6 users: Kernel Update 4 fixes 11 vulnerabilities, including high-severity CVEs CVE-2025-38087 and CVE-2025-38212. Prevent use-after-free exploits and privilege escalation. Read more:👉 https://t.co/xq0MY3ZfW9 #Security https://t.co/tRqEO

    @Cezar_H_Linux

    9 Sept 2025

    47 Impressions

    0 Retweets

    1 Like

    0 Bookmarks

    0 Replies

    0 Quotes

  20. URGENT: #SUSE patches 17 Linux kernel vulnerabilities. Multiple CVEs with 8.5 CVSS scores (e.g., CVE-2025-38212) allow local privilege escalation to root. Read more: 👉 https://t.co/OXk9ZdcCeG #Security https://t.co/EFWSQ0tazC

    @Cezar_H_Linux

    19 Aug 2025

    39 Impressions

    0 Retweets

    1 Like

    0 Bookmarks

    0 Replies

    0 Quotes

  21. CVE-2025-38212 Use-After-Free Vulnerability in Linux Kernel IPC Subsystem RCU Handling https://t.co/K9VYSmx1Q7

    @VulmonFeeds

    5 Jul 2025

    83 Impressions

    0 Retweets

    0 Likes

    0 Bookmarks

    0 Replies

    0 Quotes

Configurations

  1. In the Linux kernel, the following vulnerability has been resolved: KVM: x86/mmu: Ensure hugepage is in by slot before checking max mapping level When recovering hugepages in the shadow MMU, verify that the base gfn of the shadow page is actually contained within the target memslot, *before* querying the max mapping level given the shadow page's gfn. Failure to pre-check the validity of the gfn can lead to an out-of-bounds access to the slot's lpage_info (which typically manifests as a host #PF because the lpage_info is vmalloc'd) if the guest creates a hugepage mapping (in its PTEs) that extends "below" the bounds of a memslot. When faulting in memory for a guest, and the size of the guest mapping is greater than KVM's (current) max mapping, then KVM will create a "direct" shadow page (direct in that there are no gPTEs to shadow, and so the target gfn is a direct calculation given the base gfn of the shadow page). The hugepage recovery flow looks for such direct shadow pages, as forcing 4KiB mappings when dirty logging generates the guest > host mapping size case. When the 4KiB restriction is lifted, then KVM can replace the shadow page with a hugepage. But if KVM originally used a smaller mapping than the guest because the range of memory covered by the guest hugepage exceeds the bounds of a memslot, then KVM will link a direct shadow page with a gfn that is outside the bounds of the memslot being used to fault in memory. The rmap entry added for the leaf mapping is correct and within bounds, but the gfn of the leaf SPTE's parent shadow page will be out of bounds. BUG: unable to handle page fault for address: ffffc90000806ffc #PF: supervisor read access in kernel mode #PF: error_code(0x0000) - not-present page PGD 100000067 P4D 100000067 PUD 1002a7067 PMD 10612f067 PTE 0 Oops: Oops: 0000 [#1] SMP CPU: 13 UID: 1000 PID: 757 Comm: mmu_stress_test Not tainted 7.1.0-rc1-48ce1e26eace-x86_pir_to_irr_comments-vm #341 PREEMPT Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 0.0.0 02/06/2015 RIP: 0010:kvm_mmu_max_mapping_level+0x79/0x2b0 [kvm] Call Trace: <TASK> kvm_mmu_recover_huge_pages+0x21b/0x320 [kvm] kvm_set_memslot+0x1ee/0x590 [kvm] kvm_set_memory_region.part.0+0x3a1/0x4d0 [kvm] kvm_vm_ioctl+0x9bf/0x15d0 [kvm] __x64_sys_ioctl+0x8a/0xd0 do_syscall_64+0xb7/0xbb0 entry_SYSCALL_64_after_hwframe+0x4b/0x53 RIP: 0033:0x7f21c0f1a9bf </TASK> Don't bother pre-checking the bounds of the potential hugepage, i.e. don't check that e.g. sp->gfn + KVM_PAGES_PER_HPAGE(sp->role.level + 1) is also within the memslot, as the checks performed by kvm_mmu_max_mapping_level() are a superset of the basic bounds checks. I.e. pre-checking the full range would be a dubious micro-optimization.CVE-2026-63807
  2. In the Linux kernel, the following vulnerability has been resolved: KVM: Replace guest-triggerable BUG_ON() in ioeventfd datamatch with get_unaligned() Drop a BUG_ON() that has been reachable since it was first added, way back in 2009, and instead use get_unaligned() to perform potentially-unaligned accesses. For a given store, KVM x86's emulator tracks the entire value in the destination operand, x86_emulate_ctxt.dst. If the destination is memory, and the target splits multiple pages and/or is emulated MMIO, then KVM handles each fragment independently. E.g. on a page split starting at page offset 0xffc, KVM writes 4 bytes to the first page, then the remaining bytes to the second page, using ctxt->dst as the source for both (with appropriate offsets). If the destination splits a page *and* hits emulated MMIO on the second page, then KVM will complete the write to the first page, then emulate the MMIO access to the second page. If there is a datamatch-enabled ioeventfd at offset 0 of the second page, then KVM will process the remainder of the store as a potential ioeventfd signal. Putting it all together, if the guest emits a store that splits a page starting at page offset N, and the second page has a datamatch-enabled ioeventfd at offset 0, then KVM will check for datamatch using &dst.valptr[N] as the source. Due to dst (and thus dst.valptr) being 32-byte aligned, if N is not aligned to @len, the BUG_ON() fires. E.g. with a 16-byte store at page offset 0xffc, to an ioeventfd of len 8, all initial checks in ioeventfd_in_range() will succeed, and the BUG_ON() fires due to @val being 4-byte aligned, but not 8-byte aligned. ------------[ cut here ]------------ kernel BUG at arch/x86/kvm/../../../virt/kvm/eventfd.c:783! Oops: invalid opcode: 0000 [#1] SMP CPU: 0 UID: 1000 PID: 615 Comm: repro Not tainted 7.1.0-rc2-ff238429d1ea #365 PREEMPT Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 0.0.0 02/06/2015 RIP: 0010:ioeventfd_write+0x6c/0x70 [kvm] Call Trace: <TASK> __kvm_io_bus_write+0x85/0xb0 [kvm] kvm_io_bus_write+0x53/0x80 [kvm] vcpu_mmio_write+0x66/0xf0 [kvm] emulator_read_write_onepage+0x12a/0x540 [kvm] emulator_read_write+0x109/0x2b0 [kvm] x86_emulate_insn+0x4f8/0xfb0 [kvm] x86_emulate_instruction+0x181/0x790 [kvm] kvm_mmu_page_fault+0x313/0x630 [kvm] vmx_handle_exit+0x18a/0x590 [kvm_intel] kvm_arch_vcpu_ioctl_run+0xc81/0x1c90 [kvm] kvm_vcpu_ioctl+0x2d5/0x970 [kvm] __x64_sys_ioctl+0x8a/0xd0 do_syscall_64+0xb7/0x890 entry_SYSCALL_64_after_hwframe+0x4b/0x53 RIP: 0033:0x7f19c931a9bf </TASK> Modules linked in: kvm_intel kvm irqbypass ---[ end trace 0000000000000000 ]--- In a perfect world, the fix would be to simply delete the BUG_ON(), as KVM x86 doesn't perform alignment checks on "normal" memory accesses at CPL0. Sadly, C99 ruins all the fun; while the x86 architecture plays nice, dereferencing an unaligned pointer directly is undefined behavior in C, e.g. triggers splats when running with CONFIG_UBSAN_ALIGNMENT=y.CVE-2026-63806
  3. In the Linux kernel, the following vulnerability has been resolved: hdlc_ppp: sync per-proto timers before freeing hdlc state Each PPP control protocol (LCP/IPCP/IPV6CP) embedded in struct ppp registers a timer via timer_setup(). That struct ppp is the hdlc->state allocation, which detach_hdlc_protocol() frees with kfree() in both teardown paths: unregister_hdlc_device() and the re-attach inside attach_hdlc_protocol(). The ppp proto never registered a .detach callback, so detach_hdlc_protocol() performs no timer synchronization before the kfree(). The only cancel, timer_delete(&proto->timer) in ppp_cp_event(), is partial (it does not wait for a running callback) and only runs on the ->CLOSED transition; ppp_stop()/ppp_close() do not sync either. A ppp_timer callback already executing (blocked on ppp->lock) survives the kfree and then dereferences proto->state / ppp->lock in freed memory, leading to a use-after-free. Fix this by adding a .detach helper that calls timer_shutdown_sync() on every per-proto timer. detach_hdlc_protocol() invokes proto->detach(dev) before kfree(hdlc->state), so timer_shutdown_sync() now runs on both free paths. timer_shutdown_sync() is used instead of timer_delete_sync() because the keepalive path re-arms the timer through add_timer()/mod_timer() and shutdown blocks any re-activation during teardown. Initialize the per-protocol timers in ppp_ioctl() when the protocol is attached, and remove the now-redundant timer_setup() from ppp_start(), so that the timers are initialized exactly once at attach time and ppp_timer_release() never operates on uninitialized timer_list structures. attach_hdlc_protocol() uses kmalloc() (not kzalloc), so struct ppp's protos[i].timer is uninitialized garbage until the first timer_setup(); without this init-at-attach, attaching the PPP protocol without ever bringing the device up would leave timer_shutdown_sync() operating on uninitialized memory in .detach. Moving the init out of ppp_start() (which only runs on NETDEV_UP) into the attach path makes the initialization unconditional and avoids initializing the same timer_list twice. This bug was found by static analysis.CVE-2026-63803