x86/mm: Check return value from memblock_phys_alloc_range()
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
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.
From the CVE record · Linux
The Linux kernel’s x86 memory-management code does not check whether a memory allocation failed. With CONFIG_PHYSICAL_START=0x100000 and less than 4 MiB of contiguous free memory available at that point, the kernel can crash. The input does not describe an attacker trigger, authentication requirement, or user interaction.
Anyone running the Linux kernel with CONFIG_PHYSICAL_START=0x100000 should check whether their build includes the fix; affected versions were not provided.