CVE-2025-38071
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.
How to fix
- linux linux_kernel6.1.141, 6.6.93, 6.12.31, 6.14.9 or later
- git.kernel.org/stable/c/631ca8909fd5c62b9fda9edda93924311a78a9c4
- git.kernel.org/stable/c/8c18c904d301ffeb33b071eadc55cd6131e1e9be
- git.kernel.org/stable/c/bffd5f2815c5234d609725cd0dc2f4bc5de2fc67
- git.kernel.org/stable/c/c6f2694c580c27dca0cf7546ee9b4bfa6b940e38
- git.kernel.org/stable/c/dde4800d2b0f68b945fd81d4fc2d4a10ae25f743
Affected products
| Product | Affected versions | Fixed in |
|---|---|---|
| linux linux_kernel | v < 6.1.141, 6.2 ≤ v < 6.6.93, 6.7 ≤ v < 6.12.31, 6.13 ≤ v < 6.14.9 | 6.1.141, 6.6.93, 6.12.31, 6.14.9 |
| debian debian_linux | 11.0 | — |
Check your version
Choose the product and enter the version you run to see whether it falls in the affected range.
Attack Surface Management
See the assets tied to your domains, the technologies they run and known vulnerabilities in one list.