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
linux: linux kernel; debian: debian linux
References7
- git.kernel.org/stable/c/631ca8909fd5c62b9fda9edda93924311a78a9c4 Patch
- git.kernel.org/stable/c/8c18c904d301ffeb33b071eadc55cd6131e1e9be Patch
- git.kernel.org/stable/c/bffd5f2815c5234d609725cd0dc2f4bc5de2fc67 Patch
- git.kernel.org/stable/c/c6f2694c580c27dca0cf7546ee9b4bfa6b940e38 Patch
- git.kernel.org/stable/c/dde4800d2b0f68b945fd81d4fc2d4a10ae25f743 Patch
- lists.debian.org/debian-lts-announce/2025/10/msg00008.html Third Party Advisory
- cert-portal.siemens.com/productcert/html/ssa-082556.html
Metrics
- CVSS 3.1
-
5.5
MEDIUM
Score source: NVD
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H - EPSS — exploit probability
- 0% percentile: 9 · as of 7 November 2026
Could this be exploited in your environment?
A patch closes the known hole. A penetration test shows what an attacker can still reach — with proof.