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.
Metrics
Affected Vendors & Products
References
History
Sat, 21 Jun 2025 12:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| References |
| |
| Metrics |
threat_severity
|
cvssV3_1
|
Wed, 18 Jun 2025 09:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| 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. | |
| Title | x86/mm: Check return value from memblock_phys_alloc_range() | |
| References |
|
|
Status: PUBLISHED
Assigner: Linux
Published: 2025-06-18T09:33:47.975Z
Updated: 2025-06-18T09:33:47.975Z
Reserved: 2025-04-16T04:51:23.980Z
Link: CVE-2025-38071
No data.
Status : Awaiting Analysis
Published: 2025-06-18T10:15:40.450
Modified: 2025-06-18T13:46:52.973
Link: CVE-2025-38071