mm/mm_init: deferred_grow_zone(): fix out-of-range first_deferred_pfn
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
6.18.507.2.47.3In the Linux kernel, the following vulnerability has been resolved:
mm/mm_init: deferred_grow_zone(): fix out-of-range first_deferred_pfn
With CONFIG_DEFERRED_STRUCT_PAGE_INIT enabled, deferred_grow_zone() initializes struct pages early in boot to satisfy an allocation.
With a large CMA reservation in place, the ranges deferred_init_memmap() finds may not add up to the allocation it was asked for, and the function ends up initializing the memory map of the entire zone and still falls short.
That is fine in itself: the function accounts for it and leaves the caller to decide whether it now has enough memory.
However, the update of pgdat->first_deferred_pfn that tracks where uninitialized memory map starts could overflow.
If the node's RAM end is not aligned on PAGES_PER_SECTION boundaries and some deferred struct pages were initialized, pgdat->first_deferred_pfn would point past the end of the node's memory.
deferred_init_memmap() later picks up from pgdat->first_deferred_pfn and hits a BUG_ON(), because it expects a pfn within its node.
From the CVE record · Linux
The Linux kernel can set first_deferred_pfn past the end of a memory node during early boot when deferred struct page initialization is enabled, a large CMA reservation is present, and the node's RAM end is not section-aligned. Subsequent memory-map initialization can trigger a kernel panic; the input does not describe an attacker, authentication requirement, or user interaction.
Engineers running Linux kernels with CONFIG_DEFERRED_STRUCT_PAGE_INIT enabled and large CMA reservations should check their systems; affected versions are not specified.