mm/page_alloc: don't spin_trylock() in NMI on UP
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.
- Products
- Kernel
- Affected versions
- Not specified
- Fixed versions
- 6.18.51, 7.2.5
- CVEs
- CVE-2026-90046
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 5 Nov 2026, 01:28 UTC · Revision 1
Source evidence
mm/page_alloc: don't spin_trylock() in NMI on UP
core-osv · Original sourcePublished 16 Sept 2026, 10:33 UTC
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.
osv:CVE-2026-90046
Kernel
Fixed versions: 6.18.51, 7.2.5
Complete source record
{
"id": "023fb3cecd52e47c4ccd49e0e5ebbdc27dc57161dec163d605cc04e4eb62087b",
"url": "https://osv.dev/vulnerability/CVE-2026-90046",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "mm/page_alloc: don't spin_trylock() in NMI on UP",
"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.",
"evidence": "osv:CVE-2026-90046",
"products": [
{
"name": {
"value": "Kernel",
"evidence": "/affected/1/package/name"
},
"prerequisites": [],
"fixed_versions": [
{
"value": "6.18.51",
"evidence": "/affected/1/ranges"
},
{
"value": "7.2.5",
"evidence": "/affected/1/ranges"
}
],
"affected_versions": []
}
],
"severity": "high",
"structured": {
"id": "CVE-2026-90046",
"aliases": [
"CVE-2026-90046"
],
"metrics": [
{
"type": "CVSS_V3",
"score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H"
}
],
"affected": [
{
"ranges": [
{
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"type": "GIT",
"events": [
{
"introduced": "8c57b687e8331eb80e302a2c528b18b966a9ac7a"
},
{
"fixed": "06c76d3c389ff504052f64b1acee44651bd847fa"
},
{
"fixed": "68a069b407303e71db371df85036101e8ff59280"
},
{
"fixed": "3105ae628fb785d48b49256468be4f21a7b3cfc0"
}
]
}
],
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-90046.json"
}
},
{
"ranges": [
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.15.0"
},
{
"fixed": "6.18.51"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.19.0"
},
{
"fixed": "7.2.5"
}
]
}
],
"package": {
"name": "Kernel",
"ecosystem": "Linux"
},
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-90046.json"
}
}
],
"modified": "2026-10-28T02:30:41.115139399Z",
"provider": "osv",
"references": [
"https://git.kernel.org/stable/c/06c76d3c389ff504052f64b1acee44651bd847fa",
"https://git.kernel.org/stable/c/3105ae628fb785d48b49256468be4f21a7b3cfc0",
"https://git.kernel.org/stable/c/68a069b407303e71db371df85036101e8ff59280",
"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/90xxx/CVE-2026-90046.json",
"https://nvd.nist.gov/vuln/detail/CVE-2026-90046",
"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git"
],
"provider_metadata": {
"cna_assigner": "Linux",
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/90xxx/CVE-2026-90046.json"
}
},
"related_cves": [
{
"value": "CVE-2026-90046",
"evidence": "/id"
}
],
"security_relevant": true,
"severity_evidence": "/severity/0/score"
},
"source_id": "core-osv",
"document_id": 509085,
"published_at": "2026-09-16T10:33:43.156+00:00"
}