CVE-2026-53063

MEDIUMNVD 5.55.5—
EchelonGraph scoreHIGH confidence

Score 5.5 from GitHub Security Advisory published 2026-06-24. NVD baseline CVSS 5.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Trending — 5 sources updated this week
5.5
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 5.5Exploit: NoneExposed: 0

A fix is available — apply it.

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.

CVSS v3
5.5
EG Score
5.5(high)
EPSS
2.8%
KEV
Not listed

Published

June 24, 2026

Last Modified

July 21, 2026

Advisory Details (6)

Auto-updated Jul 21, 2026
No patch confirmed yet.
generic

dm cache: fix write hang in passthrough mode - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/ecb10c193cbebf5e6984246a9b4ff1f95d45ed87
generic

dm cache: fix write hang in passthrough mode - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/b8ace9e96983abb20ccf39edce8a60f1bb0b83d8
generic

dm cache: fix write hang in passthrough mode - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/9fa18d0b981776b190ca4632942a7c2174052b78
generic

dm cache: fix write hang in passthrough mode - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/64d6519b00be4116d365bd31f33a5e5ce2944c1a
generic

dm cache: fix write hang in passthrough mode - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/4ca8b8bd952df7c3ccdc68af9bd3419d0839a04b
generic

dm cache: fix write hang in passthrough mode - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/05798d091ebcfb6d68228890e593f209e8ac940d

Vendor Advisories for CVE-2026-53063(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(4)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-virtual-hwe-24.04-edge (7.0.0-28.28~24.04.1) @ noble2026-07-21ubuntu
ubuntulinux-virtual-hwe-26.04-edge (7.0.0-28.28) @ resolute2026-07-21ubuntu
ubuntulinux-tools-oem-7.0 (7.0.0-1009.9) @ resolute2026-07-21ubuntu
ubuntulinux-virtual-6.8 (6.8.0-136.136) @ noble2026-07-21ubuntu

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Additional Vendor Advisories

(4)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 16× in last 7d / 57× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-22 14:08 UTCEPSS rescore
  2. 2026-07-21 19:19 UTCEG score recompute▲ 5.50
  3. 2026-07-21 19:19 UTCVendor advisory
  4. 2026-07-21 19:19 UTCGHSA enrichment
  5. 2026-07-21 19:19 UTCNVD updateCVSS v3 → 5.5 · severity → MEDIUM
  6. 2026-07-21 15:25 UTCEPSS rescore
  7. 2026-07-20 17:08 UTCEPSS rescore
  8. 2026-07-19 14:31 UTCEPSS rescore
  9. 2026-07-19 14:31 UTCEPSS rescore
  10. 2026-07-19 02:29 UTCEPSS rescore
  11. 2026-07-18 10:04 UTCEPSS rescore
  12. 2026-07-16 20:14 UTCVendor advisory
  13. 2026-07-16 20:14 UTCGHSA enrichment
  14. 2026-07-16 17:03 UTCEPSS rescore
  15. 2026-07-15 16:57 UTCEPSS rescore
  16. 2026-07-15 16:57 UTCEPSS rescore
  17. 2026-07-15 02:00 UTCEPSS rescore
  18. 2026-07-15 02:00 UTCEPSS rescore
  19. 2026-07-14 00:57 UTCVendor advisory
  20. 2026-07-14 00:57 UTCGHSA enrichment
  21. 2026-07-13 22:31 UTCEPSS rescore
  22. 2026-07-13 06:13 UTCEPSS rescore
  23. 2026-07-13 06:13 UTCEPSS rescore
  24. 2026-07-12 05:46 UTCEPSS rescore
  25. 2026-07-11 08:27 UTCEPSS rescore
Show 32 more
  1. 2026-07-11 08:27 UTCEPSS rescore
  2. 2026-07-11 06:52 UTCVendor advisory
  3. 2026-07-11 06:52 UTCGHSA enrichment
  4. 2026-07-09 19:10 UTCEPSS rescore
  5. 2026-07-09 19:10 UTCEPSS rescore
  6. 2026-07-08 15:16 UTCEPSS rescore
  7. 2026-07-08 15:16 UTCEPSS rescore
  8. 2026-07-08 12:48 UTCGHSA enrichment
  9. 2026-07-07 13:46 UTCEPSS rescore
  10. 2026-07-07 13:46 UTCEPSS rescore
  11. 2026-07-06 16:27 UTCEPSS rescore
  12. 2026-07-06 16:27 UTCEPSS rescore
  13. 2026-07-06 02:23 UTCEPSS rescore
  14. 2026-07-06 02:23 UTCEPSS rescore
  15. 2026-07-05 18:32 UTCGHSA enrichment
  16. 2026-07-05 02:31 UTCEPSS rescore
  17. 2026-07-05 02:30 UTCEPSS rescore
  18. 2026-07-04 06:31 UTCEPSS rescore
  19. 2026-07-03 00:27 UTCGHSA enrichment
  20. 2026-07-01 15:07 UTCEPSS rescore
  21. 2026-06-30 23:22 UTCEPSS rescore
  22. 2026-06-30 06:23 UTCGHSA enrichment
  23. 2026-06-29 14:06 UTCEPSS rescore
  24. 2026-06-29 14:06 UTCEPSS rescore
  25. 2026-06-28 14:07 UTCEPSS rescore
  26. 2026-06-28 04:56 UTCEPSS rescore
  27. 2026-06-28 04:56 UTCEPSS rescore
  28. 2026-06-27 12:20 UTCGHSA enrichment
  29. 2026-06-27 03:08 UTCEPSS rescore
  30. 2026-06-25 13:49 UTCEPSS rescore
  31. 2026-06-24 18:16 UTCEG score recompute
  32. 2026-06-24 18:03 UTCNVD updatefirst tracked

Related CVEs(same vendor)

Frequently asked(5)

What is CVE-2026-53063?
CVE-2026-53063 is a medium vulnerability published on June 24, 2026. 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…
When was CVE-2026-53063 disclosed?
CVE-2026-53063 was first published in the National Vulnerability Database on June 24, 2026, with the most recent update on July 21, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-53063 actively exploited?
CVE-2026-53063 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 2.8% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-53063?
CVE-2026-53063 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-53063?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-53063, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-53063

Explore →

Is Your Infrastructure Affected by CVE-2026-53063?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs