Answer in brief
CVE-2026-93230 records a Unknown severity vulnerability in mm/hugetlb: initialize gigantic bootmem hugepage struct pages earlier. 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 | >=fde1c4ecf91640e5a95ec36b71ec2e8ec379ce40 <09505232eced5f1c42902d8f28740f070c3fc6dc || >=fde1c4ecf91640e5a95ec36b71ec2e8ec379ce40 <29968bc7aefb3cf1e72aa7c5f52697a6b0527094 || >=fde1c4ecf91640e5a95ec36b71ec2e8ec379ce40 <b1b7c045e808c761b1cc8c19b3040fadedda3fef | 09505232eced5f1c42902d8f28740f070c3fc6dc, 29968bc7aefb3cf1e72aa7c5f52697a6b0527094, b1b7c045e808c761b1cc8c19b3040fadedda3fef |
| Linux/Linuxgeneric | 6.7 | Not reported |
Published upstream
Sep 24, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Sep 24, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Sep 25, 2026
In the Linux kernel, the following vulnerability has been resolved: mm/hugetlb: initialize gigantic bootmem hugepage struct pages earlier Gigantic bootmem HugeTLB pages are currently initialized from hugetlb_init(), but page_alloc_init_late() runs earlier and walks pageblocks to determine zone contiguity. If a bootmem HugeTLB region is marked noinit, set_zone_contiguous() can observe still-uninitialized struct pages through __pageblock_pfn_to_page(). This may not trigger an immediate failure, but it can make set_zone_contiguous() compute the wrong zone contiguity state. If extra poisoned-page checks are added in this path, such as PF_POISONED_CHECK() in page_zone_id(), it can also trigger an early boot panic. Initialize gigantic bootmem HugeTLB struct pages from page_alloc_init_late(), before zone contiguity is evaluated, so later page allocator setup only sees valid struct page state. This also makes the initialization order more natural, as struct pages should be initialized before later code inspects them.
Quoted source text, attributed separately from HOL analysis.