Description
In the Linux kernel, the following vulnerability has been resolved: x86/mm: Check return value from memblock_phys_alloc_range() At least with CONFIG_PHYSICAL_START=0x100000, if there is < 4 MiB of contiguous free memory available at this point, the kernel will crash and burn because memblock_phys_alloc_range() returns 0 on failure, which leads memblock_phys_free() to throw the first 4 MiB of physical memory to the wolves. At a minimum it should fail gracefully with a meaningful diagnostic, but in fact everything seems to work fine without the weird reserve allocation.
Affected products
Version statuses are supplied by the assigning organization. Consult the original record for detailed ranges and platform conditions.
Linux Linux
Default version status: unaffected
a7259df7670240ee03b0cfce8a3e5d3773911e24 to < 8c18c904d301ffeb33b071eadc55cd6131e1e9beaffecteda7259df7670240ee03b0cfce8a3e5d3773911e24 to < bffd5f2815c5234d609725cd0dc2f4bc5de2fc67affecteda7259df7670240ee03b0cfce8a3e5d3773911e24 to < c6f2694c580c27dca0cf7546ee9b4bfa6b940e38affecteda7259df7670240ee03b0cfce8a3e5d3773911e24 to < dde4800d2b0f68b945fd81d4fc2d4a10ae25f743affecteda7259df7670240ee03b0cfce8a3e5d3773911e24 to < 631ca8909fd5c62b9fda9edda93924311a78a9c4affected
Linux Linux
Default version status: affected
5.15affected0 to < 5.15unaffected6.1.141 to ≤ 6.1.*unaffected6.6.93 to ≤ 6.6.*unaffected6.12.31 to ≤ 6.12.*unaffected6.14.9 to ≤ 6.14.*unaffected6.15 to ≤ *unaffected
References
- https://git.kernel.org/stable/c/8c18c904d301ffeb33b071eadc55cd6131e1e9be ↗
- https://git.kernel.org/stable/c/bffd5f2815c5234d609725cd0dc2f4bc5de2fc67 ↗
- https://git.kernel.org/stable/c/c6f2694c580c27dca0cf7546ee9b4bfa6b940e38 ↗
- https://git.kernel.org/stable/c/dde4800d2b0f68b945fd81d4fc2d4a10ae25f743 ↗
- https://git.kernel.org/stable/c/631ca8909fd5c62b9fda9edda93924311a78a9c4 ↗
- https://lists.debian.org/debian-lts-announce/2025/10/msg00008.html ↗
- https://cert-portal.siemens.com/productcert/html/ssa-082556.html ↗