Skip to main content
VulnerabilityPublished Updated

CVE-2026-53063: Linux kernel · dm cache: fix write hang in passthrough mode

Affects Linux kernelSource CVE Database V5

0
Compare

Not known to be exploited · fixed in ecb10c193cbebf5e6984246a9b4ff1f95d45ed87 : update Linux kernel when convenient.

Data as of 6 Nov 2026, 16:49 UTC

Severity
Unrated

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

  1. Disclosed: evidence found.

    CVE published 24 Jun 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ b29d4986d0da1a27cd35917cdb433672f5c95d7f, < ecb10c193cbebf5e6984246a9b4ff1f95d45ed87
Fixed in
  • ecb10c193cbebf5e6984246a9b4ff1f95d45ed87
LinuxLinuxAffected
  • ≥ b29d4986d0da1a27cd35917cdb433672f5c95d7f, < b8ace9e96983abb20ccf39edce8a60f1bb0b83d8
Fixed in
  • b8ace9e96983abb20ccf39edce8a60f1bb0b83d8
LinuxLinuxAffected
  • ≥ b29d4986d0da1a27cd35917cdb433672f5c95d7f, < 05798d091ebcfb6d68228890e593f209e8ac940d
Fixed in
  • 05798d091ebcfb6d68228890e593f209e8ac940d
LinuxLinuxAffected
  • ≥ b29d4986d0da1a27cd35917cdb433672f5c95d7f, < 64d6519b00be4116d365bd31f33a5e5ce2944c1a
Fixed in
  • 64d6519b00be4116d365bd31f33a5e5ce2944c1a
LinuxLinuxAffected
  • ≥ b29d4986d0da1a27cd35917cdb433672f5c95d7f, < 9fa18d0b981776b190ca4632942a7c2174052b78
Fixed in
  • 9fa18d0b981776b190ca4632942a7c2174052b78
LinuxLinuxAffected
  • ≥ b29d4986d0da1a27cd35917cdb433672f5c95d7f, < 4ca8b8bd952df7c3ccdc68af9bd3419d0839a04b
Fixed in
  • 4ca8b8bd952df7c3ccdc68af9bd3419d0839a04b

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

Community reviews

Loading reviews…