Answer in brief
CVE-2026-72212 records a Unknown severity vulnerability in mm/memory_hotplug: fix incorrect altmap passing in error path. 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.
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.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=6b8f0798b85aa529011570369db985a788f3003f <3833e6abdbbfb59ec8203a84a84206cb7ffb41ac || >=6b8f0798b85aa529011570369db985a788f3003f <722e6c54bde6391fb95f0357f555aca887c7b18c || >=6b8f0798b85aa529011570369db985a788f3003f <2f9e3ec17c3d2093c664c00a027588a446c39894 || >=6b8f0798b85aa529011570369db985a788f3003f <2fac4afa0e2e68841334c78c1821e49f74fbc66a | 3833e6abdbbfb59ec8203a84a84206cb7ffb41ac, 722e6c54bde6391fb95f0357f555aca887c7b18c, 2f9e3ec17c3d2093c664c00a027588a446c39894, 2fac4afa0e2e68841334c78c1821e49f74fbc66a |
| Linux/Linuxgeneric | 6.8 | Not reported |
Published upstream
Aug 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 15, 2026
In the Linux kernel, the following vulnerability has been resolved: mm/memory_hotplug: fix incorrect altmap passing in error path In create_altmaps_and_memory_blocks(), when arch_add_memory() succeeds with memmap_on_memory enabled, the vmemmap pages are allocated from params.altmap. If create_memory_block_devices() subsequently fails, the error path calls arch_remove_memory() with a NULL altmap instead of params.altmap. This is a bug that could lead to memory corruption. Since altmap is NULL, vmemmap_free() falls back to freeing the vmemmap pages into the system buddy allocator via free_pages() instead of the altmap. arch_remove_memory() then immediately destroys the physical linear mapping for this memory. This injects unowned pages into the buddy allocator, causing machine checks or memory corruption if the system later attempts to allocate and use those freed pages. Fix this by passing params.altmap to arch_remove_memory() in the error path.
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2026-72212 records a Unknown severity vulnerability in mm/memory_hotplug: fix incorrect altmap passing in error path. 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.
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.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=6b8f0798b85aa529011570369db985a788f3003f <3833e6abdbbfb59ec8203a84a84206cb7ffb41ac || >=6b8f0798b85aa529011570369db985a788f3003f <722e6c54bde6391fb95f0357f555aca887c7b18c || >=6b8f0798b85aa529011570369db985a788f3003f <2f9e3ec17c3d2093c664c00a027588a446c39894 || >=6b8f0798b85aa529011570369db985a788f3003f <2fac4afa0e2e68841334c78c1821e49f74fbc66a | 3833e6abdbbfb59ec8203a84a84206cb7ffb41ac, 722e6c54bde6391fb95f0357f555aca887c7b18c, 2f9e3ec17c3d2093c664c00a027588a446c39894, 2fac4afa0e2e68841334c78c1821e49f74fbc66a |
| Linux/Linuxgeneric | 6.8 | Not reported |
Published upstream
Aug 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 15, 2026
In the Linux kernel, the following vulnerability has been resolved: mm/memory_hotplug: fix incorrect altmap passing in error path In create_altmaps_and_memory_blocks(), when arch_add_memory() succeeds with memmap_on_memory enabled, the vmemmap pages are allocated from params.altmap. If create_memory_block_devices() subsequently fails, the error path calls arch_remove_memory() with a NULL altmap instead of params.altmap. This is a bug that could lead to memory corruption. Since altmap is NULL, vmemmap_free() falls back to freeing the vmemmap pages into the system buddy allocator via free_pages() instead of the altmap. arch_remove_memory() then immediately destroys the physical linear mapping for this memory. This injects unowned pages into the buddy allocator, causing machine checks or memory corruption if the system later attempts to allocate and use those freed pages. Fix this by passing params.altmap to arch_remove_memory() in the error path.
Quoted source text, attributed separately from HOL analysis.