x86/mm: Check return value from memblock_phys_alloc_range()
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 6.1.141, 6.6.93, 6.12.31, 6.14.9
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
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.
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
From a7259df7670240ee03b0cfce8a3e5d3773911e24 · fixed in 8c18c904d301ffeb33b071eadc55cd6131e1e9be; From a7259df7670240ee03b0cfce8a3e5d3773911e24 · fixed in bffd5f2815c5234d609725cd0dc2f4bc5de2fc67; From a7259df7670240ee03b0cfce8a3e5d3773911e24 · fixed in c6f2694c580c27dca0cf7546ee9b4bfa6b940e38; From a7259df7670240ee03b0cfce8a3e5d3773911e24 · fixed in dde4800d2b0f68b945fd81d4fc2d4a10ae25f743; From a7259df7670240ee03b0cfce8a3e5d3773911e24 · fixed in 631ca8909fd5c62b9fda9edda93924311a78a9c4
- Linux Linux
5.15
- KernelLinux
From 5.15.0 · fixed in 6.1.141; From 6.2.0 · fixed in 6.6.93; From 6.7.0 · fixed in 6.12.31; From 6.13.0 · fixed in 6.14.9