dm-pcache: validate the persisted dirty_tail chain at load
- 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.52, 7.2.6
- 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: validate the persisted dirty_tail chain at load The writeback worker follows the persisted dirty_tail chain, which is decoded from the cache device independently of the key_tail chain that cache_replay() walks and bounds. A crafted image, whose on-media fields are authenticated only by a crc32c with a fixed seed, can aim dirty_tail at a chain of last ksets that never terminates, so cache_writeback_fn() re-arms itself with no delay forever. Walk the dirty_tail chain once at load with the same hop cap cache_replay() uses and fail the table load with -EIO if it does not reach an end within n_segs hops.
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
From 1d57628ff95b32d5cfa8d8f50e07690c161e9cf0 · fixed in 8195cf3f4a82ef49d9b0651c507ed0784caf23fb; From 1d57628ff95b32d5cfa8d8f50e07690c161e9cf0 · fixed in 4822a030929e0e77aa380722dc42e3e4c9edd346; From 1d57628ff95b32d5cfa8d8f50e07690c161e9cf0 · fixed in 58d620ee9e01d4bdbceaf2ae1450d307a2a9d58b
- Linux Linux
6.18
- KernelLinux
From 6.18.0 · fixed in 6.18.52; From 6.19.0 · fixed in 7.2.6