GHSA-3775-XR2M-86HX
Vulnerability from github – Published: 2026-09-17 18:32 – Updated: 2026-09-17 18:32In 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
{
"affected": [],
"aliases": [
"CVE-2026-93172"
],
"database_specific": {
"cwe_ids": [],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-09-17T17:18:12Z",
"severity": null
},
"details": "In the Linux kernel, the following vulnerability has been resolved:\n\nmm/mm_init: handle alloc_percpu failure in free_area_init_core_hotplug\n\nWe miss a failed allocation check for pgdat-\u003eper_cpu_nodestats, which\nresults in a NULL deref when we offset into the per-cpu area.\n\nPropagate -ENOMEM up the stack and leave per_cpu_nodestats pointing\nat boot_nodestats so a later online can retry the allocation.\n\nhotadd_init_pgdat() returns NULL on failure, which __try_online_node()\nalready maps to -ENOMEM.\n\nOn failure nothing needs to be unwound:\n - the node is never marked online\n - per_cpu_nodestats is left pointing at boot_nodestats\n - __add_memory_resource() cleans up pending memblock resources\n - later online attempts retry the per_cpu_nodestats allocation",
"id": "GHSA-3775-xr2m-86hx",
"modified": "2026-09-17T18:32:13Z",
"published": "2026-09-17T18:32:13Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-93172"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/1017fe1c7f48e511c5a680e3057005daaff2f3a2"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/2ebce860bdd7ae5e13002811bc9bbbf33fcfc221"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/4cc5caef9a8d1894dfa31d84a0daa0ac1437dadc"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/bc3b5e6519b8df22d622a03eab6772784da97db4"
}
],
"schema_version": "1.4.0",
"severity": []
}
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.