AZL-93458
See a problem?- Import Source
- https://github.com/microsoft/AzureLinuxVulnerabilityData/blob/main/osv/AZL-93458.json
- JSON Data
- https://api.osv.dev/v1/vulns/AZL-93458
- Upstream
- Published
- 2026-07-25T10:17:14Z
- Modified
- 2026-08-28T17:47:48.412026544Z
- Summary
- CVE-2026-64326 affecting package kernel for versions less than 6.6.145.2-1
- Details
-
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 fsbdevmarkdead() honours this and skips syncfilesystem(), but the bare block device path (no ->markdead op) lost its !surprise guard when the holder ->markdead 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 nvmeresetwork()'s "I/O queues lost" path: nvmemarknamespacesdead() -> blkmarkdiskdead() -> bdevmarkdead(bdev, true) -> syncblockdev() blocks in foliowait_writeback(), wedging the reset worker and every task waiting on it.
Skip the sync on surprise removal, matching fsbdevmarkdead(); invalidatebdev() still runs. Orderly removal (surprise == false) is unchanged.
Found by FuzzNvme(Syzkaller with FEMU fuzzing framework).
- References