mm/mm_init: handle alloc_percpu failure in free_area_init_core_hotplug
In the Linux kernel, the following vulnerability has been resolved: mm/mm_init: handle alloc_percpu failure in free_area_init_core_hotplug We miss a failed allocation check for pgdat->per_cpu_nodestats, which results in a NULL deref when we offset into the per-cpu area. Propagate -ENOMEM up the stack and leave per_cpu_nodestats pointing at boot_nodestats so a later online can retry the allocation. hotadd_init_pgdat() returns NULL on failure, which __try_online_node() already maps to -ENOMEM. On failure nothing needs to be unwound: - the node is never marked online - per_cpu_nodestats is left pointing at boot_nodestats - __add_memory_resource() cleans up pending memblock resources - later online attempts retry the per_cpu_nodestats allocation
- Products
- Kernel
- Affected versions
- Not specified
- Fixed versions
- 6.1.191, 6.12.110, 6.18.52, 6.6.160, 7.2.6
- CVEs
- CVE-2026-93172
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 3 Nov 2026, 17:12 UTC · Revision 1
Source evidence
mm/mm_init: handle alloc_percpu failure in free_area_init_core_hotplug
core-osv · Original sourcePublished 17 Sept 2026, 16:12 UTC
In the Linux kernel, the following vulnerability has been resolved: mm/mm_init: handle alloc_percpu failure in free_area_init_core_hotplug We miss a failed allocation check for pgdat->per_cpu_nodestats, which results in a NULL deref when we offset into the per-cpu area. Propagate -ENOMEM up the stack and leave per_cpu_nodestats pointing at boot_nodestats so a later online can retry the allocation. hotadd_init_pgdat() returns NULL on failure, which __try_online_node() already maps to -ENOMEM. On failure nothing needs to be unwound: - the node is never marked online - per_cpu_nodestats is left pointing at boot_nodestats - __add_memory_resource() cleans up pending memblock resources - later online attempts retry the per_cpu_nodestats allocation
osv:CVE-2026-93172
Kernel
Fixed versions: 6.1.191, 6.6.160, 6.12.110, 6.18.52, 7.2.6
Complete source record
{
"id": "fbd1181b31171b47dfc13e1383534a0c88b879f3daeffad73df728d93b9f1f0f",
"url": "https://osv.dev/vulnerability/CVE-2026-93172",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "mm/mm_init: handle alloc_percpu failure in free_area_init_core_hotplug",
"summary": "In the Linux kernel, the following vulnerability has been resolved: mm/mm_init: handle alloc_percpu failure in free_area_init_core_hotplug We miss a failed allocation check for pgdat->per_cpu_nodestats, which results in a NULL deref when we offset into the per-cpu area. Propagate -ENOMEM up the stack and leave per_cpu_nodestats pointing at boot_nodestats so a later online can retry the allocation. hotadd_init_pgdat() returns NULL on failure, which __try_online_node() already maps to -ENOMEM. On failure nothing needs to be unwound: - the node is never marked online - per_cpu_nodestats is left pointing at boot_nodestats - __add_memory_resource() cleans up pending memblock resources - later online attempts retry the per_cpu_nodestats allocation",
"evidence": "osv:CVE-2026-93172",
"products": [
{
"name": {
"value": "Kernel",
"evidence": "/affected/1/package/name"
},
"prerequisites": [],
"fixed_versions": [
{
"value": "6.1.191",
"evidence": "/affected/1/ranges"
},
{
"value": "6.6.160",
"evidence": "/affected/1/ranges"
},
{
"value": "6.12.110",
"evidence": "/affected/1/ranges"
},
{
"value": "6.18.52",
"evidence": "/affected/1/ranges"
},
{
"value": "7.2.6",
"evidence": "/affected/1/ranges"
}
],
"affected_versions": []
}
],
"severity": "unknown",
"structured": {
"id": "CVE-2026-93172",
"aliases": [
"CVE-2026-93172"
],
"affected": [
{
"ranges": [
{
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"type": "GIT",
"events": [
{
"introduced": "75ef7184053989118d3814c558a9af62e7376a58"
},
{
"fixed": "eb872b92e26c2576742d541e45f28b50af059b8b"
},
{
"fixed": "4dda09e7ca0bf0c3fa7c5c8f134d9804b67f455c"
},
{
"fixed": "4cc5caef9a8d1894dfa31d84a0daa0ac1437dadc"
},
{
"fixed": "bc3b5e6519b8df22d622a03eab6772784da97db4"
},
{
"fixed": "1017fe1c7f48e511c5a680e3057005daaff2f3a2"
},
{
"fixed": "2ebce860bdd7ae5e13002811bc9bbbf33fcfc221"
}
]
}
],
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-93172.json"
}
},
{
"ranges": [
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "4.8.0"
},
{
"fixed": "6.1.191"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.2.0"
},
{
"fixed": "6.6.160"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.7.0"
},
{
"fixed": "6.12.110"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.13.0"
},
{
"fixed": "6.18.52"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.19.0"
},
{
"fixed": "7.2.6"
}
]
}
],
"package": {
"name": "Kernel",
"ecosystem": "Linux"
},
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-93172.json"
}
}
],
"modified": "2026-11-01T02:30:33.252379756Z",
"provider": "osv",
"references": [
"https://git.kernel.org/stable/c/1017fe1c7f48e511c5a680e3057005daaff2f3a2",
"https://git.kernel.org/stable/c/2ebce860bdd7ae5e13002811bc9bbbf33fcfc221",
"https://git.kernel.org/stable/c/4cc5caef9a8d1894dfa31d84a0daa0ac1437dadc",
"https://git.kernel.org/stable/c/4dda09e7ca0bf0c3fa7c5c8f134d9804b67f455c",
"https://git.kernel.org/stable/c/bc3b5e6519b8df22d622a03eab6772784da97db4",
"https://git.kernel.org/stable/c/eb872b92e26c2576742d541e45f28b50af059b8b",
"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/93xxx/CVE-2026-93172.json",
"https://nvd.nist.gov/vuln/detail/CVE-2026-93172",
"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/93xxx/CVE-2026-93172.json"
}
},
"related_cves": [
{
"value": "CVE-2026-93172",
"evidence": "/id"
}
],
"security_relevant": true,
"severity_evidence": null
},
"source_id": "core-osv",
"document_id": 497736,
"published_at": "2026-09-17T16:12:02.544+00:00"
}