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.
Published: 2026-09-24
Score: n/a
EPSS: < 1% Very Low
KEV: No
Impact: Boot-time Denial of Service
Action: Apply patch
AI Analysis

Impact

This vulnerability arises when the Linux kernel’s HugeTLB page structures for gigantic boot memory are not initialized early enough. The missing initialization allows the later zone contiguity routine to observe partially constructed page structures, leading to an incorrect determination of memory zone contiguity. If additional checks, such as poisoned‑page validations, are triggered in that path, the kernel can panic during early boot. The immediate effect is a boot‑time failure that renders the system unusable until a reboot or repair is performed, representing a denial of service at start‑up.

Affected Systems

All Linux kernel variants that lack the fix are affected, regardless of distribution vendor. The issue is within the core kernel, making it applicable to any system running an affected kernel version. Because no specific release numbers are indicated, you should review your kernel to confirm whether it incorporates the initialization fix to assess potential impact.

Risk and Exploitability

The kernel crash is a severe outcome, but the vulnerability is limited to the boot environment and requires physical or privileged access to modify boot parameters or the kernel image. No EPSS score is available and the vulnerability is not listed in CISA’s KEV catalog, indicating no public exploitation reports yet. However, the nature of the bug—improper initialization leading to a kernel panic—suggests a high intrinsic impact for systems that cannot be readily patched. The likely attack vector is an attacker with the ability to influence the system boot, such as a malicious bootloader or disk image, which could trigger the panic or indirectly destabilize the system.

Generated by OpenCVE AI on September 25, 2026 at 11:59 UTC.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Update the Linux kernel to a version that incorporates the fix for this issue.
  • Ensure that no bootmem HugeTLB regions are marked noinit during system configuration; adjust kernel command line parameters or sysctl settings to prevent the use of uninitialized regions if possible.
  • If an immediate kernel update is not feasible, consider disabling HugeTLB support for boot memory or applying a custom kernel module that initializes the relevant struct pages early, recognizing that this is a temporary workaround and may not be fully reliable.

Generated by OpenCVE AI on September 25, 2026 at 11:59 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Fri, 25 Sep 2026 12:15:00 +0000

Type Values Removed Values Added
Weaknesses CWE-665

Thu, 24 Sep 2026 15:30:00 +0000

Type Values Removed Values Added
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.
Title mm/hugetlb: initialize gigantic bootmem hugepage struct pages earlier
First Time appeared Linux
Linux linux Kernel
CPEs cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
Vendors & Products Linux
Linux linux Kernel
References

Subscriptions

Linux Linux Kernel
cve-icon MITRE

Status: PUBLISHED

Assigner: Linux

Published:

Updated: 2026-09-24T15:29:16.067Z

Reserved: 2026-09-17T16:02:15.094Z

Link: CVE-2026-93230

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Received

Published: 2026-09-24T16:17:18.517

Modified: 2026-09-24T16:17:18.517

Link: CVE-2026-93230

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-09-25T12:00:15Z

Weaknesses