hugetlb: only adjust reservation during unmapping if mapcount is 0
- 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.12.110, 6.18.50, 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: hugetlb: only adjust reservation during unmapping if mapcount is 0 Since df7a6d1f6405, __unmap_hugepage_range can adjust reservations. In the case of folio mapped in both a parent and a child, if the parent unmaps the range first, the reservation adjustment will result in an underflow of the reserved count. Once the child unmaps the range, the count is restored. Change __unmap_hugepage_range() to check the mapcount before adjusting the reservation.
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
From df7a6d1f64056aec572162c5d35ed9ff86ece6f3 · fixed in b0b1b9ca80b795ed2223e76dd787db7067121fb9; From df7a6d1f64056aec572162c5d35ed9ff86ece6f3 · fixed in a3c65af20cceb7f997847727636b4017326f845d; From df7a6d1f64056aec572162c5d35ed9ff86ece6f3 · fixed in 0f001491e5a2ec69aa9d5dd6b799e5742245f9ea; From df7a6d1f64056aec572162c5d35ed9ff86ece6f3 · fixed in 5120b1e048d48596ffaec1a8412012a91adba73b
- Linux Linux
6.9
- KernelLinux
From 6.9.0 · fixed in 6.12.110; From 6.13.0 · fixed in 6.18.50; From 6.19.0 · fixed in 7.2.4