mm/page_alloc: don't spin_trylock() in NMI on UP
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 6.18.51, 7.2.5
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
In the Linux kernel, the following vulnerability has been resolved: mm/page_alloc: don't spin_trylock() in NMI on UP Patch series "mm/page_alloc: fixes for free_pages_nolock() on RT/UP". Pre-existing bugs found by Sashiko during review of this other series: https://lore.kernel.org/all/20260703-alloc-trylock-v5-0-c87b714e19d3@google.com/ I have not reproduced these bugs, and I suspect there is no real-world user that is affected by them. This patch (of 2): As noted in can_spin_trylock(), using this is unsafe in this context. commit 620b46ed6ae17 ("mm/page_alloc: return NULL early from alloc_frozen_pages_nolock() in NMI on UP") fixed this on the alloc side but missed the free side. Impact: If BPF programs using these features in NMI (probably tracing) are present on non-SMP builds this might crash the kernel and is probably exploitable by local attackers for privilege escalation.
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
From 8c57b687e8331eb80e302a2c528b18b966a9ac7a · fixed in 06c76d3c389ff504052f64b1acee44651bd847fa; From 8c57b687e8331eb80e302a2c528b18b966a9ac7a · fixed in 68a069b407303e71db371df85036101e8ff59280; From 8c57b687e8331eb80e302a2c528b18b966a9ac7a · fixed in 3105ae628fb785d48b49256468be4f21a7b3cfc0
- Linux Linux
6.15
- KernelLinux
From 6.15.0 · fixed in 6.18.51; From 6.19.0 · fixed in 7.2.5