dm cache: fix write hang in passthrough mode
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ b29d4986d0da1a27cd35917cdb433672f5c95d7f · < 4ca8b8bd952df7c3ccdc68af9bd3419d0839a04b| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
dm cache: fix write hang in passthrough mode
The invalidate_remove() function has incomplete logic for handling write hit bios after cache invalidation. It sets up the remapping for the overwrite_bio but then drops it immediately without submission, causing write operations to hang.
Fix by adding a new invalidate_committed() continuation that submits the remapped writes to the cache origin after metadata commit completes, while using the overwrite_endio hook to ensure proper completion sequencing. This maintains existing coherency. Also improve error handling in invalidate_complete() to preserve the original error status instead of using bio_io_error() unconditionally.
From the CVE record · Linux
In dm cache passthrough mode, a write hit after cache invalidation can hang because the remapped write is not submitted. An attacker able to trigger this condition could cause write operations to hang; the input does not specify an access path, authentication requirement, or user interaction.
Operators running Linux kernels that use dm cache passthrough mode should check their kernel; affected versions are not specified.