dm-pcache: bound the persisted tail-position offset
- 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.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: dm-pcache: bound the persisted tail-position offset cache_pos_decode() takes the persisted key_tail and dirty_tail seg_off from the cache device and addresses within the segment with it. A seg_off at or past the segment data_size, controllable by whoever supplies the device (CAP_SYS_ADMIN), reads past the segment data. Reject a decoded seg_off that is not below the segment data_size.
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
From 1d57628ff95b32d5cfa8d8f50e07690c161e9cf0 · fixed in ffd9a214a94f9928e54856f42b1cc3e33fb10e36; From 1d57628ff95b32d5cfa8d8f50e07690c161e9cf0 · fixed in 8bf7a06ca3c1611809725f58cfd573f2ffbda75f; From 1d57628ff95b32d5cfa8d8f50e07690c161e9cf0 · fixed in d1898576090a10d2ac2715218a652e78fb65a6b0
- Linux Linux
6.18
- KernelLinux
From 6.18.0 · fixed in 6.18.50; From 6.19.0 · fixed in 7.2.4