CVE-2026-64326

UNRATEDCVSS · not yet scoredTrending — 3 sources updated this week
—
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • No CVSS published and no exploitation signals yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS v2: —Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

In the Linux kernel, the following vulnerability has been resolved:

block: skip sync_blockdev() on surprise removal in bdev_mark_dead()

bdev_mark_dead()'s @surprise == true means the device is already gone. The filesystem callback fs_bdev_mark_dead() honours this and skips sync_filesystem(), but the bare block device path (no ->mark_dead op) lost its !surprise guard when the holder ->mark_dead callback was wired up (see Fixes), and now calls sync_blockdev() unconditionally, which can hang forever waiting on writeback that can no longer complete.

syzkaller hit this via nvme_reset_work()'s "I/O queues lost" path: nvme_mark_namespaces_dead() -> blk_mark_disk_dead() -> bdev_mark_dead(bdev, true) -> sync_blockdev() blocks in folio_wait_writeback(), wedging the reset worker and every task waiting on it.

Skip the sync on surprise removal, matching fs_bdev_mark_dead(); invalidate_bdev() still runs. Orderly removal (surprise == false) is unchanged.

Found by FuzzNvme(Syzkaller with FEMU fuzzing framework).

CVSS v3
—
EchelonGraph score
Not yet assessedNo source has published severity data for this CVE yet — no CVSS score from NVD or a CNA, no GitHub advisory, and it is not in CISA KEV. This is not a rating of zero; we cannot assess it yet.
EG Score
—
EG Risk
—
EPSS PROB
0%
EPSS %ILE
11%
KEV
Not listed

Published

July 25, 2026

Last Modified

August 17, 2026

References (5)

Vendor Advisories for CVE-2026-64326(2)

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

Affected Packages

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux-6.12—6.12.100-1~deb12u1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.95-1~bpo12+1 (30 versions)6.12.96-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.1~rc7-1~exp1 (156 versions)7.1.4-1—

Data Freshness Timeline

(refreshed 10× in last 7d / 45× 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-08-30 01:22 UTCEPSS rescore
  2. 2026-08-30 00:10 UTCVendor advisory
  3. 2026-08-30 00:10 UTCGHSA enrichment
  4. 2026-08-28 21:42 UTCEPSS rescore
  5. 2026-08-26 14:47 UTCEPSS rescore
  6. 2026-08-26 10:39 UTCVendor advisory
  7. 2026-08-26 10:39 UTCGHSA enrichment
  8. 2026-08-25 13:49 UTCEPSS rescore
  9. 2026-08-23 08:18 UTCVendor advisory
  10. 2026-08-23 08:18 UTCGHSA enrichment
  11. 2026-08-23 00:19 UTCEPSS rescore
  12. 2026-08-21 23:49 UTCEPSS rescore
  13. 2026-08-20 22:55 UTCEPSS rescore
  14. 2026-08-20 06:49 UTCGHSA enrichment
  15. 2026-08-19 17:04 UTCEPSS rescore
  16. 2026-08-18 13:48 UTCEPSS rescore
  17. 2026-08-17 13:47 UTCEPSS rescore
  18. 2026-08-17 05:25 UTCNVD update
  19. 2026-08-17 05:20 UTCVendor advisory
  20. 2026-08-17 05:20 UTCGHSA enrichment
  21. 2026-08-17 05:05 UTCMITRE cvelistV5
  22. 2026-08-16 14:56 UTCEPSS rescore
  23. 2026-08-15 01:30 UTCEPSS rescore
  24. 2026-08-14 16:37 UTCVendor advisory
  25. 2026-08-14 16:37 UTCGHSA enrichment
Show 36 more
  1. 2026-08-13 22:00 UTCEPSS rescore
  2. 2026-08-12 13:51 UTCEPSS rescore
  3. 2026-08-11 15:08 UTCVendor advisory
  4. 2026-08-11 15:08 UTCGHSA enrichment
  5. 2026-08-11 00:00 UTCEPSS rescore
  6. 2026-08-10 10:30 UTCGHSA enrichment
  7. 2026-08-09 13:47 UTCEPSS rescore
  8. 2026-08-08 16:37 UTCEPSS rescore
  9. 2026-08-07 09:01 UTCGHSA enrichment
  10. 2026-08-06 13:47 UTCEPSS rescore
  11. 2026-08-05 19:17 UTCEPSS rescore
  12. 2026-08-05 19:17 UTCEPSS rescore
  13. 2026-08-04 15:10 UTCEPSS rescore
  14. 2026-08-04 10:39 UTCEPSS rescore
  15. 2026-08-04 07:32 UTCGHSA enrichment
  16. 2026-08-03 10:36 UTCEPSS rescore
  17. 2026-08-02 02:27 UTCEPSS rescore
  18. 2026-08-01 05:52 UTCEG score recompute
  19. 2026-08-01 05:51 UTCGHSA enrichment
  20. 2026-08-01 04:16 UTCEPSS rescore
  21. 2026-07-30 16:28 UTCEPSS rescore
  22. 2026-07-30 01:30 UTCEPSS rescore
  23. 2026-07-30 01:30 UTCEPSS rescore
  24. 2026-07-29 04:20 UTCEG score recompute
  25. 2026-07-29 04:20 UTCGHSA enrichment
  26. 2026-07-28 15:37 UTCEPSS rescore
  27. 2026-07-27 14:14 UTCEPSS rescore
  28. 2026-07-26 14:54 UTCEPSS rescore
  29. 2026-07-26 14:54 UTCEPSS rescore
  30. 2026-07-26 02:51 UTCEG score recompute
  31. 2026-07-26 02:50 UTCGHSA enrichment
  32. 2026-07-25 14:18 UTCEPSS rescore
  33. 2026-07-25 14:18 UTCEPSS rescore
  34. 2026-07-25 10:39 UTCNVD update
  35. 2026-07-25 09:37 UTCEG score recompute
  36. 2026-07-25 09:21 UTCMITRE cvelistV5first tracked

Frequently asked(4)

What is CVE-2026-64326?
CVE-2026-64326 is a publicly disclosed vulnerability published on July 25, 2026. In the Linux kernel, the following vulnerability has been resolved: block: skip syncblockdev() on surprise removal in bdevmark_dead() bdevmarkdead()'s @surprise == true means the device is already gone. The filesystem callback fsbdevmark_dead() honours this and skips syncfilesystem(), but the bare…
When was CVE-2026-64326 disclosed?
CVE-2026-64326 was first published in the National Vulnerability Database on July 25, 2026, with the most recent update on August 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-64326 actively exploited?
CVE-2026-64326 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 89.5% of all scored CVEs.
How do I remediate CVE-2026-64326?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-64326, 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

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-64326

Explore →

Is Your Infrastructure Affected by CVE-2026-64326?

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

Start Free Scan →Browse All CVEs