# CVE-2026-93230: mm/hugetlb: initialize gigantic bootmem hugepage struct pages earlier

> Improper initialization of gigantic bootmem hugepages can cause early boot panics or incorrect zone contiguity states in the Linux kernel.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 24 Sep 2026
- **Updated:** 21 Oct 2026
- **Also known as:** BELL-CVE-2026-93230, DEBIAN-CVE-2026-93230, GHSA-cvcw-r3xv-6h39, UBUNTU-CVE-2026-93230

## What is CVE-2026-93230?

CVE-2026-93230 is a denial of service vulnerability in Linux, published on 24 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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.

## Which versions are affected by CVE-2026-93230?


## How do I fix CVE-2026-93230?

Apply the vendor's patch.

## Is CVE-2026-93230 being exploited?

There is no known exploitation of CVE-2026-93230 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-93230 and fix it if it is affected.

What it is: CVE-2026-93230 is a denial of service vulnerability in Linux, published on 24 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-93230 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-93230/ (Markdown: https://insights.sbomify.com/CVE-2026-93230/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-93230
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-93230
- OSV: https://osv.dev/vulnerability/CVE-2026-93230

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-93230/
Summaries are generated and may contain mistakes; the official description above is the record.