CVE-2026-64326block: skip sync_blockdev() on surprise removal in bdev_mark_dead()
- 5.5MediumCVSS base score
- 0.16%Exploitation in 30 daysEPSS · top 95% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
Description
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).
Timeline
ID reserved
By Linux
- 6 days later
· 6 days later
Published
- 3 months later
· 3 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
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| NVDNVD · Analyzed | 3.1 | Medium5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
- EPSS (exploitation in 30 days)
- 0.16% · top 95% of all CVEs (15 Nov 2026)
- CISA SSVC
- Exploitation: none · Automatable: no · Technical impact: partial
The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.
Affected products
- affected d8530de5a6e82be0ce17a5fdf727a394bcf6444c – < d6998ddd507c81e3829489a6ead23f17f5acb7fe
- affected d8530de5a6e82be0ce17a5fdf727a394bcf6444c – < f41cf35ee2a1e31374b3f54e7579c55153506e70
- affected d8530de5a6e82be0ce17a5fdf727a394bcf6444c – < 9818bcae3c0ca1dde4b9a334125c46676e0a9b29
- affected d8530de5a6e82be0ce17a5fdf727a394bcf6444c – < aa4c4a9315764b2b7a7182e72cc5ea87520436b4
- affected d8530de5a6e82be0ce17a5fdf727a394bcf6444c – < 49f06cff50a4ccf3b7a1a662ceb892b3b21a527a
- affected 6.6
- unaffected < 6.6
- unaffected 6.6.145 – ≤ 6.6.*
- unaffected 6.12.96 – ≤ 6.12.*
- unaffected 6.18.39 – ≤ 6.18.*
- unaffected 7.1.4 – ≤ 7.1.*
- unaffected 7.2 – ≤ *
References
References5
- https://git.kernel.org/stable/c/d6998ddd507c81e3829489a6ead23f17f5acb7fe (opens in a new tab)
- https://git.kernel.org/stable/c/f41cf35ee2a1e31374b3f54e7579c55153506e70 (opens in a new tab)
- https://git.kernel.org/stable/c/9818bcae3c0ca1dde4b9a334125c46676e0a9b29 (opens in a new tab)
- https://git.kernel.org/stable/c/aa4c4a9315764b2b7a7182e72cc5ea87520436b4 (opens in a new tab)
- https://git.kernel.org/stable/c/49f06cff50a4ccf3b7a1a662ceb892b3b21a527a (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-48870 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-64326)Record last updated .