mm/mm_init: handle alloc_percpu failure in free_area_init_core_hotplug (CVE-2026-93172) | HOL Guard CVE

Unknown severity · Source severity not reportedCVE-2026-93172

mm/mm_init: handle alloc_percpu failure in free_area_init_core_hotplug

Answer in brief

CVE-2026-93172 records a Unknown severity vulnerability in mm/mm_init: handle alloc_percpu failure in free_area_init_core_hotplug. 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 17, 2026Updated Sep 17, 2026Source checked Sep 17, 2026First seen by HOL Sep 17, 2026Material review Sep 17, 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	>=75ef7184053989118d3814c558a9af62e7376a58 <4cc5caef9a8d1894dfa31d84a0daa0ac1437dadc \|\| >=75ef7184053989118d3814c558a9af62e7376a58 <bc3b5e6519b8df22d622a03eab6772784da97db4 \|\| >=75ef7184053989118d3814c558a9af62e7376a58 <1017fe1c7f48e511c5a680e3057005daaff2f3a2 \|\| >=75ef7184053989118d3814c558a9af62e7376a58 <2ebce860bdd7ae5e13002811bc9bbbf33fcfc221	4cc5caef9a8d1894dfa31d84a0daa0ac1437dadc, bc3b5e6519b8df22d622a03eab6772784da97db4, 1017fe1c7f48e511c5a680e3057005daaff2f3a2, 2ebce860bdd7ae5e13002811bc9bbbf33fcfc221
Linux/Linuxgeneric	4.8	Not reported

Recommended response

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

Evidence timeline and material changes

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

Sources and claim methodology

Upstream source description

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

Quoted source text, attributed separately from HOL analysis.