mm/page_alloc: don't spin_trylock() in NMI on UP (CVE-2026-90046) | HOL Guard CVE

Unknown severity · Source severity not reportedCVE-2026-90046

mm/page_alloc: don't spin_trylock() in NMI on UP

Answer in brief

CVE-2026-90046 records a Unknown severity vulnerability in mm/page_alloc: don't spin_trylock() in NMI on UP. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Sep 16, 2026Updated Sep 16, 2026Source checked Sep 16, 2026First seen by HOL Sep 16, 2026Material review Sep 16, 2026

Upstream Advisory

Key facts

Risk: Unknown severitySource severity not reported
Exploitation: Not marked as known exploited
Affected software: 2 mapped packages or products
Fix availability: Available

Why this deserves its current priority

A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
Linux/Linuxgeneric	>=8c57b687e8331eb80e302a2c528b18b966a9ac7a <06c76d3c389ff504052f64b1acee44651bd847fa \|\| >=8c57b687e8331eb80e302a2c528b18b966a9ac7a <68a069b407303e71db371df85036101e8ff59280 \|\| >=8c57b687e8331eb80e302a2c528b18b966a9ac7a <3105ae628fb785d48b49256468be4f21a7b3cfc0	06c76d3c389ff504052f64b1acee44651bd847fa, 68a069b407303e71db371df85036101e8ff59280, 3105ae628fb785d48b49256468be4f21a7b3cfc0
Linux/Linuxgeneric	6.15	Not reported

Recommended response

Check inventory. Check lockfiles and deployed manifests for Linux/Linux, Linux/Linux.
Review the reported fix. Update Linux/Linux to 06c76d3c389ff504052f64b1acee44651bd847fa if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

Published upstream
Sep 16, 2026
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Sep 16, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Sep 16, 2026

Sources and claim methodology

Upstream source description

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/[email protected]/ 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.

Quoted source text, attributed separately from HOL analysis.