Goal Reached Thanks to every supporter — we hit 100%!

Goal: 1000 CNY · Raised: 1359 CNY

100%

CVE-2026-23025— mm/page_alloc: prevent pcp corruption with SMP=n

Quick assessment

Affected
Linux Linux
Exploitation
No confirmed in-the-wild exploitation; assess based on exposure
Recommended action
Check the vendor advisory and references for a fixed version. If immediate upgrade is impossible, restrict exposure and increase monitoring.

Linux kernel是美国Linux基金会的开源操作系统Linux所使用的内核。 Linux kernel存在安全漏洞,该漏洞源于SMP=n时可能导致pcp损坏。

AI Predicted 5.5 Difficulty: Moderate EPSS 0.21% · P10

Possible ATT&CK Techniques 1 AI

T1059 · Command and Scripting Interpreter

Affected Version Matrix 13

VendorProduct Version RangeStatus
Linux Linux d1da921452b3ee7e07383c12955ab1c6f3b08752< 68688fc4eab007834b4c2d740214423ba2a335a8 affected
5749077415994eb02d660b2559b9d8278521e73d< 4a04ff9cd816e7346fcc8126f00ed80481f6569d affected
5749077415994eb02d660b2559b9d8278521e73d< df63d31e9ae02e2f6cd96147779e4ed7cd0e75f6 affected
5749077415994eb02d660b2559b9d8278521e73d< 3098f8f7c7b0686c74827aec42a2c45e69801ff8 affected
5749077415994eb02d660b2559b9d8278521e73d< 038a102535eb49e10e93eafac54352fcc5d78847 affected
6.1.57< 6.1.162 affected
6.2 affected
< 6.2 unaffected
… +5 more rows
Get alerts for future matching vulnerabilities Log in to subscribe

I. Basic Information for CVE-2026-23025

Vulnerability Information

Have questions about the vulnerability? See if Shenlong's analysis helps!
View Shenlong Deep Dive ↗

Although we use advanced large model technology, its output may still contain inaccurate or outdated information.Shenlong tries to ensure data accuracy, but please verify and judge based on the actual situation.

Vulnerability Title
mm/page_alloc: prevent pcp corruption with SMP=n
Source: CVE Program / CVE List V5
Vulnerability Description
In the Linux kernel, the following vulnerability has been resolved: mm/page_alloc: prevent pcp corruption with SMP=n The kernel test robot has reported: BUG: spinlock trylock failure on UP on CPU#0, kcompactd0/28 lock: 0xffff888807e35ef0, .magic: dead4ead, .owner: kcompactd0/28, .owner_cpu: 0 CPU: 0 UID: 0 PID: 28 Comm: kcompactd0 Not tainted 6.18.0-rc5-00127-ga06157804399 #1 PREEMPT 8cc09ef94dcec767faa911515ce9e609c45db470 Call Trace: <IRQ> __dump_stack (lib/dump_stack.c:95) dump_stack_lvl (lib/dump_stack.c:123) dump_stack (lib/dump_stack.c:130) spin_dump (kernel/locking/spinlock_debug.c:71) do_raw_spin_trylock (kernel/locking/spinlock_debug.c:?) _raw_spin_trylock (include/linux/spinlock_api_smp.h:89 kernel/locking/spinlock.c:138) __free_frozen_pages (mm/page_alloc.c:2973) ___free_pages (mm/page_alloc.c:5295) __free_pages (mm/page_alloc.c:5334) tlb_remove_table_rcu (include/linux/mm.h:? include/linux/mm.h:3122 include/asm-generic/tlb.h:220 mm/mmu_gather.c:227 mm/mmu_gather.c:290) ? __cfi_tlb_remove_table_rcu (mm/mmu_gather.c:289) ? rcu_core (kernel/rcu/tree.c:?) rcu_core (include/linux/rcupdate.h:341 kernel/rcu/tree.c:2607 kernel/rcu/tree.c:2861) rcu_core_si (kernel/rcu/tree.c:2879) handle_softirqs (arch/x86/include/asm/jump_label.h:36 include/trace/events/irq.h:142 kernel/softirq.c:623) __irq_exit_rcu (arch/x86/include/asm/jump_label.h:36 kernel/softirq.c:725) irq_exit_rcu (kernel/softirq.c:741) sysvec_apic_timer_interrupt (arch/x86/kernel/apic/apic.c:1052) </IRQ> <TASK> RIP: 0010:_raw_spin_unlock_irqrestore (arch/x86/include/asm/preempt.h:95 include/linux/spinlock_api_smp.h:152 kernel/locking/spinlock.c:194) free_pcppages_bulk (mm/page_alloc.c:1494) drain_pages_zone (include/linux/spinlock.h:391 mm/page_alloc.c:2632) __drain_all_pages (mm/page_alloc.c:2731) drain_all_pages (mm/page_alloc.c:2747) kcompactd (mm/compaction.c:3115) kthread (kernel/kthread.c:465) ? __cfi_kcompactd (mm/compaction.c:3166) ? __cfi_kthread (kernel/kthread.c:412) ret_from_fork (arch/x86/kernel/process.c:164) ? __cfi_kthread (kernel/kthread.c:412) ret_from_fork_asm (arch/x86/entry/entry_64.S:255) </TASK> Matthew has analyzed the report and identified that in drain_page_zone() we are in a section protected by spin_lock(&pcp->lock) and then get an interrupt that attempts spin_trylock() on the same lock. The code is designed to work this way without disabling IRQs and occasionally fail the trylock with a fallback. However, the SMP=n spinlock implementation assumes spin_trylock() will always succeed, and thus it's normally a no-op. Here the enabled lock debugging catches the problem, but otherwise it could cause a corruption of the pcp structure. The problem has been introduced by commit 574907741599 ("mm/page_alloc: leave IRQs enabled for per-cpu page allocations"). The pcp locking scheme recognizes the need for disabling IRQs to prevent nesting spin_trylock() sections on SMP=n, but the need to prevent the nesting in spin_lock() has not been recognized. Fix it by introducing local wrappers that change the spin_lock() to spin_lock_iqsave() with SMP=n and use them in all places that do spin_lock(&pcp->lock). [vbabka@suse.cz: add pcp_ prefix to the spin_lock_irqsave wrappers, per Steven]
Source: CVE Program / CVE List V5
CVSS Information
N/A
Source: CVE Program / CVE List V5
Vulnerability Type
N/A
Source: CVE Program / CVE List V5
Vulnerability Title
Linux kernel 安全漏洞
Source: CNNVD (China National Vulnerability Database)
Vulnerability Description
Linux kernel是美国Linux基金会的开源操作系统Linux所使用的内核。 Linux kernel存在安全漏洞,该漏洞源于SMP=n时可能导致pcp损坏。
Source: CNNVD (China National Vulnerability Database)
CVSS Information
N/A
Source: CNNVD (China National Vulnerability Database)
Vulnerability Type
N/A
Source: CNNVD (China National Vulnerability Database)

Affected Products

Vendor Product Affected Versions CPE Subscribe
Linux Linux d1da921452b3ee7e07383c12955ab1c6f3b08752 ~ 68688fc4eab007834b4c2d740214423ba2a335a8 -
Linux Linux 6.2 -

II. Public POCs for CVE-2026-23025

# POC Description Source Link Shenlong Link
AI-Generated POC Premium

No public POC found.

Login to generate AI POC

III. Intelligence Information for CVE-2026-23025

请登录查看更多情报信息。

Same Patch Batch · Linux · 2026-01-31 · 37 CVEs total

CVE-2025-71183 9.1 CRITICAL btrfs: always detect conflicting inodes when logging inode refs
CVE-2026-23018 btrfs: release path before initializing extent tree in btrfs_read_locked_inode()
CVE-2025-71186 dmaengine: stm32: dmamux: fix device leak on route allocation
CVE-2025-71185 dmaengine: ti: dma-crossbar: fix device leak on am335x route allocation
CVE-2026-23024 idpf: fix memory leak of flow steer list on rmmod
CVE-2026-23023 idpf: fix memory leak in idpf_vport_rel()
CVE-2026-23022 idpf: fix memory leak in idpf_vc_core_deinit()
CVE-2026-23021 net: usb: pegasus: fix memory leak in update_eth_regs_async()
CVE-2026-23020 net: 3com: 3c59x: fix possible null dereference in vortex_probe1()
CVE-2026-23019 net: marvell: prestera: fix NULL dereference on devlink_alloc() failure
CVE-2025-71187 dmaengine: sh: rz-dmac: fix device leak on probe failure
CVE-2026-23017 idpf: fix error handling in the init_task on load
CVE-2026-23016 inet: frags: drop fraglist conntrack references
CVE-2026-23015 gpio: mpsse: fix reference leak in gpio_mpsse_probe() error paths
CVE-2025-71184 btrfs: fix NULL dereference on root when tracing inode eviction
CVE-2025-71182 can: j1939: make j1939_session_activate() fail if device is no longer registered
CVE-2025-71181 rust_binder: remove spin_lock() in rust_shrink_free_page()
CVE-2025-71180 counter: interrupt-cnt: Drop IRQF_NO_THREAD flag
CVE-2026-23031 can: gs_usb: gs_usb_receive_bulk_callback(): fix URB memory leak
CVE-2026-23039 drm/gud: fix NULL fb and crtc dereferences on USB disconnect

Showing top 20 of 37 CVEs. View all on vendor page &rarr; →

IV. Related Vulnerabilities

V. Comments for CVE-2026-23025

No comments yet


Leave a comment