dm-pcache: validate the persisted dirty_tail chain at load
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
6.18.527.2.67.3In 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.
From the CVE record · Linux
The Linux kernel’s dm-pcache component does not validate a persisted dirty_tail chain when loading a cache image. A crafted image can make the writeback worker re-arm itself without delay indefinitely; the input does not specify how an attacker would get the image loaded.
Engineers running Linux systems that use dm-pcache should check their kernel versions; affected versions are not specified.