CVE-2026-53063: Linux kernel · dm cache: fix write hang in passthrough mode
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in ecb10c193cbebf5e6984246a9b4ff1f95d45ed87 : update Linux kernel when convenient.
Data as of 6 Nov 2026, 16:49 UTC
Rated by Threat Radar · No CVSS score from NVD or the CNA
Thin evidence
One scorer or none- CISA SSVC
- Exploitation
- No evidence of active exploitation and no public proof of concept
- Automatable
- Attackers cannot reliably automate steps 1–4 of the kill chain
- Technical impact
- Limited control over the software or limited information exposure
CISA SSVC assessment, 2026-11-06.
- Patch
- Available – fixed in ecb10c193cbebf5e6984246a9b4ff1f95d45ed87, b8ace9e96983abb20ccf39edce8a60f1bb0b83d8, 05798d091ebcfb6d68228890e593f209e8ac940d +3
Exploitation evidence
Disclosed: evidence found.
CVE published 24 Jun 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 6 Nov 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
Description
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.
References
- git.kernel.org/stable/c/9fa18d0b981776b190ca4632942a7c2174052b78 (opens in a new tab)
- git.kernel.org/stable/c/ecb10c193cbebf5e6984246a9b4ff1f95d45ed87 (opens in a new tab)
- git.kernel.org/stable/c/64d6519b00be4116d365bd31f33a5e5ce2944c1a (opens in a new tab)
- git.kernel.org/stable/c/b8ace9e96983abb20ccf39edce8a60f1bb0b83d8 (opens in a new tab)
- git.kernel.org/stable/c/05798d091ebcfb6d68228890e593f209e8ac940d (opens in a new tab)
- git.kernel.org/stable/c/4ca8b8bd952df7c3ccdc68af9bd3419d0839a04b (opens in a new tab)