Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

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

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.

Timeline

  1. ID reserved

    By Linux

  2. · 15 days later

    Published

  3. · 5 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2026-53063, by who scored it
Scored byCVSSScoreVector
NVDNVD · Analyzed3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.13% · top 97% of all CVEs (19 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.

Affected products

  • Linux · Linux

    • affected b29d4986d0da1a27cd35917cdb433672f5c95d7f – < 9fa18d0b981776b190ca4632942a7c2174052b78
    • affected b29d4986d0da1a27cd35917cdb433672f5c95d7f – < ecb10c193cbebf5e6984246a9b4ff1f95d45ed87
    • affected b29d4986d0da1a27cd35917cdb433672f5c95d7f – < 64d6519b00be4116d365bd31f33a5e5ce2944c1a
    • affected b29d4986d0da1a27cd35917cdb433672f5c95d7f – < b8ace9e96983abb20ccf39edce8a60f1bb0b83d8
    • affected b29d4986d0da1a27cd35917cdb433672f5c95d7f – < 05798d091ebcfb6d68228890e593f209e8ac940d
    • affected b29d4986d0da1a27cd35917cdb433672f5c95d7f – < 4ca8b8bd952df7c3ccdc68af9bd3419d0839a04b
  • Linux · Linux

    • affected 4.12
    • unaffected < 4.12
    • unaffected 6.1.175 – ≤ 6.1.*
    • unaffected 6.6.141 – ≤ 6.6.*
    • unaffected 6.12.91 – ≤ 6.12.*
    • unaffected 6.18.33 – ≤ 6.18.*
    • unaffected 7.0.10 – ≤ 7.0.*
    • unaffected 7.1 – ≤ *

References

References6

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-53063 badge
[![CVE-2026-53063](https://cveledger.app/badge/CVE-2026-53063.svg)](https://cveledger.app/cve/CVE-2026-53063)

Record last updated .