Answer in brief
CVE-2026-64302 records a Unknown severity vulnerability in x86/mm: Fix freeing of PMD-sized vmemmap pages. 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 | >=a1593c90896babf33e947910c7aecb9f50bab993 <add1e4112e00b619614784bf630aeebfdefa23e1 || >=bf9e4e30f3538391745a99bc2268ec4f5e4a401e <03f6ecbc446c33b38fd452cd3c494092a8116967 || >=bf9e4e30f3538391745a99bc2268ec4f5e4a401e <39406c05f8f150f1685839acd38ffdd69ff92031 || >=6.18.7 <6.18.39 | add1e4112e00b619614784bf630aeebfdefa23e1, 03f6ecbc446c33b38fd452cd3c494092a8116967, 39406c05f8f150f1685839acd38ffdd69ff92031, 6.18.39 |
| Linux/Linuxgeneric | 6.19 | Not reported |
Published upstream
Jul 25, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 17, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 11, 2026
In the Linux kernel, the following vulnerability has been resolved: x86/mm: Fix freeing of PMD-sized vmemmap pages Commit bf9e4e30f353 ("x86/mm: use pagetable_free()"), switched from freeing non-boot page tables through __free_pages() to pagetable_free(). However, the function is also called to free vmemmap pages. Given that vmemmap pages are not page tables, already the page_ptdesc(page) is wrong. But worse, pagetable_free() calls: __free_pages(page, compound_order(page)); Since vmemmap pages are not compound pages (see vmemmap_alloc_block()) -- except for HVO, which doesn't apply here -- only first page of a PMD-sized vmemmap page is freed, leaking the other ones. Fix it by properly decoupling pagetable and vmemmap freeing. free_pagetable() no longer has to mess with SECTION_INFO, as only the vmemmap is marked like that in register_page_bootmem_memmap(). The indentation in remove_pmd_table() is messed up. Fix that while touching it. Bootmem info handling will soon be fixed up. For now, handle it similar to free_pagetable(), just avoiding the ifdef. [ dhansen: changelog munging. More imperative voice ]
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2026-64302 records a Unknown severity vulnerability in x86/mm: Fix freeing of PMD-sized vmemmap pages. 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 | >=a1593c90896babf33e947910c7aecb9f50bab993 <add1e4112e00b619614784bf630aeebfdefa23e1 || >=bf9e4e30f3538391745a99bc2268ec4f5e4a401e <03f6ecbc446c33b38fd452cd3c494092a8116967 || >=bf9e4e30f3538391745a99bc2268ec4f5e4a401e <39406c05f8f150f1685839acd38ffdd69ff92031 || >=6.18.7 <6.18.39 | add1e4112e00b619614784bf630aeebfdefa23e1, 03f6ecbc446c33b38fd452cd3c494092a8116967, 39406c05f8f150f1685839acd38ffdd69ff92031, 6.18.39 |
| Linux/Linuxgeneric | 6.19 | Not reported |
Published upstream
Jul 25, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 17, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 11, 2026
In the Linux kernel, the following vulnerability has been resolved: x86/mm: Fix freeing of PMD-sized vmemmap pages Commit bf9e4e30f353 ("x86/mm: use pagetable_free()"), switched from freeing non-boot page tables through __free_pages() to pagetable_free(). However, the function is also called to free vmemmap pages. Given that vmemmap pages are not page tables, already the page_ptdesc(page) is wrong. But worse, pagetable_free() calls: __free_pages(page, compound_order(page)); Since vmemmap pages are not compound pages (see vmemmap_alloc_block()) -- except for HVO, which doesn't apply here -- only first page of a PMD-sized vmemmap page is freed, leaking the other ones. Fix it by properly decoupling pagetable and vmemmap freeing. free_pagetable() no longer has to mess with SECTION_INFO, as only the vmemmap is marked like that in register_page_bootmem_memmap(). The indentation in remove_pmd_table() is messed up. Fix that while touching it. Bootmem info handling will soon be fixed up. For now, handle it similar to free_pagetable(), just avoiding the ifdef. [ dhansen: changelog munging. More imperative voice ]
Quoted source text, attributed separately from HOL analysis.