CVE-2026-64326

CVE CVE-2026-64326EUVD EUVD-2026-48870Published 2026-07-25T08:49:54.000Z

What the advisory describes

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).

Source: EUVD (ENISA), in the words of the advisory.

Products the advisory names

These come from the advisory itself, not from any check we performed.

Linux — Linux patch: 7.2-rc1; patch: 7.1.4; d8530de5a6e82be0ce17a5fdf727a394bcf6444c <49f06cff50a4ccf3b7a1a662ceb892b3b21a527a; patch: 6.18.39; d8530de5a6e82be0ce17a5fdf727a394bcf6444c <9818bcae3c0ca1dde4b9a334125c46676e0a9b29; d8530de5a6e82be0ce17a5fdf727a394bcf6444c <aa4c4a9315764b2b7a7182e72cc5ea87520436b4; patch: 6.6.145; d8530de5a6e82be0ce17a5fdf727a394bcf6444c <f41cf35ee2a1e31374b3f54e7579c55153506e70; d8530de5a6e82be0ce17a5fdf727a394bcf6444c <d6998ddd507c81e3829489a6ead23f17f5acb7fe; patch: 6.12.96; patch: 0; 6.6

The versions shown are the advisory's own. Patchlage compares no version numbers and derives no judgement from them — which version is installed is something a person has to look up.

Carried in the product catalogue

An estate covering these products can be recorded in Patchlage. An advisory about them appears in the next morning's situation report.

Linux — Linux

Does this concern one of your customers?

This page cannot answer that — it does not know your estate. Whoever has recorded their environments gets the answer the morning after publication, together with a paragraph they can forward to the customer unedited.

Try it for 28 days

Patchlage reports hits and suspected hits. About everything else this system says nothing — neither this page nor the situation report ever claims that an estate is safe.