kho: fix size calculation in kho_preserved_memory_reserve()
- 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.18.57, 7.2.4
- 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: kho: fix size calculation in kho_preserved_memory_reserve() kho_preserved_memory_reserve() calculates the size of a preservation by doing 1 << (order + PAGE_SHIFT). Since the '1' is a 32-bit integer, it can only be shifted by 31. That is, it will only work for preservations up to 2 GiB. Larger preservations will trigger undefined behaviour. While preservations larger than 2 GiB can't be obtained via folios currently, they can be obtained via kho_preserve_pages(). For example, memblock reserve_mem uses kho_preserve_pages(). Reservations larger than 2 GiB are valid and will trigger this bug if properly aligned. Fix it by using 1UL for shifting.
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
From fc33e4b44b2717feba2f6f07ce7943a96499c9ec · fixed in 0692a8fdf0222af130c8ea97426f1c3bf3814905; From fc33e4b44b2717feba2f6f07ce7943a96499c9ec · fixed in 42a6f03cf352eb6e6dbeef95e75e686f4cdb9bd1; From fc33e4b44b2717feba2f6f07ce7943a96499c9ec · fixed in 3a0b8fa2eb36afc88b62a95f33f0c77c71fa5ded
- Linux Linux
6.16
- KernelLinux
From 6.16.0 · fixed in 6.18.57; From 6.19.0 · fixed in 7.2.4