Independent & educational platform Not a government body. No link or affiliation with any government organisation. Made for learning only. Test only systems you own or are authorised to test. Become a Partner or Sponsor → Full disclaimer

CVE-2026-64326

medium

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 @s…

Vendor / product: Linux — linux kernel

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
5.5
5.5 (CVSS v3.1)
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Severity source: NVD CVSS v3.1 (nvd@nist.gov)
Timeline (UTC)
Published: 2026-07-25 10:17
Modified: 2026-11-06 17:18
NVD status: Analyzed
Last synced 1 week ago
Verified against the source API 2026-11-06 17:47 UTC
Exploitation
Not listed in CISA KEV (as of last catalog sync)
Absence from KEV does not mean a CVE is not exploited. Exploitation status: unknown (no authoritative evidence in our sources).

Affected products

linux / linux_kernel ≥6.6 <6.6.145, ≥6.7 <6.12.96, ≥6.13 <6.18.39, ≥6.19 <7.1.4

Weakness classification (CWE)

NVD-CWE-noinfo

Source: NVD / CISA. “NVD-CWE-Other” and “NVD-CWE-noinfo” mean NVD could not assign a specific weakness.

Mitigation & advisories

Patch / mitigation: https://git.kernel.org/stable/c/49f06cff50a4ccf3b7a1a662ceb892b3b21a527a
Patch / mitigation: https://git.kernel.org/stable/c/9818bcae3c0ca1dde4b9a334125c46676e0a9b29
Patch / mitigation: https://git.kernel.org/stable/c/aa4c4a9315764b2b7a7182e72cc5ea87520436b4
Patch / mitigation: https://git.kernel.org/stable/c/d6998ddd507c81e3829489a6ead23f17f5acb7fe
Patch / mitigation: https://git.kernel.org/stable/c/f41cf35ee2a1e31374b3f54e7579c55153506e70

References

Data sources

NVD CVE API 2.0 — fetched 2026-11-06 17:47 UTC · record ↗

Learn the basics

Understanding CVEs and CVSS Scores

Related CVEs