CVE-2025-38071
x86/mm: Check return value from memblock_phys_alloc_range()
Using Linux by Linux?
Get instant alerts when new vulnerabilities affect Linux - before attackers find them.
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
Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.
Remediation
No guide yetNo remediation guidance has been written for this CVE yet. What the record does show:
Patch and advisory references
- https://git.kernel.org/stable/c/631ca8909fd5c62b9fda9edda93924311a78a9c4
- 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
References (7)
CVSS
- Attack Vector
- LOCAL
- Complexity
- LOW
- Privileges
- LOW
- User Interaction
- NONE
- Scope
- UNCHANGED
- Confidentiality
- NONE
- Integrity
- NONE
- Availability
- HIGH
Quick Info
Get alerted
Stop reading CVE feeds looking for your own stack
Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.