CVE-2026-64326
Last modified
CVE-2026-64326 is a medium-severity vulnerability rated 5.5/10 on the CVSS scale. 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).. EPSS estimates a 0.21% chance of exploitation in the next 30 days.
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).
Metrics
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux Kernel | >= 6.6, < 6.6.145 |
| Linux | Linux Kernel | >= 6.7, < 6.12.96 |
| Linux | Linux Kernel | >= 6.13, < 6.18.39 |
| Linux | Linux Kernel | >= 6.19, < 7.1.4 |
References
Timeline
- Published
- Last Modified
- Status
- Analyzed
Frequently Asked Questions
What is CVE-2026-64326?
How severe is CVE-2026-64326?
How do I fix CVE-2026-64326?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-64320In the Linux kernel, the following vulnerability has been re…9.1
- CVE-2026-64321In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-64322In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-64323In the Linux kernel, the following vulnerability has been re…7.1
- CVE-2026-64324In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-64325In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-64327In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-64328In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-64329In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-6433The Custom css-js-php WordPress plugin through 2.0.7 does no…7.3
- CVE-2026-64330In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-64331In the Linux kernel, the following vulnerability has been re…5.5
Are you affected by CVE-2026-64326?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
