CVE-2026-74572

CVE CVE-2026-74572EUVD EUVD-2026-59637Published 2026-08-15T12:28:11.000ZLast changed 2026-08-17T05:48:51.000ZCVSS 7.5

What the advisory describes

In the Linux kernel, the following vulnerability has been resolved: btrfs: zoned: fix deadlock between metadata writeback and transaction commit When writing out metadata extent buffers in a zoned filesystem, btree_writepages() holds fs_info->zoned_meta_io_lock across the whole writeback loop, including the call to btrfs_check_meta_write_pointer() -> check_bg_is_active(). For the tree-log block group, check_bg_is_active() may fail to activate the zone and fall back to btrfs_zone_finish_one_bg() to free an active zone. That path waits for the running transaction to commit while still holding zoned_meta_io_lock, but the committer needs that same lock to write out the tree extents, so the two tasks deadlock: Task A (kworker, metadata writeback) Task B (fsstress, transaction commit) ------------------------------------ ------------------------------------- wb_workfn() btrfs_commit_transaction(T) btree_writepages() btrfs_write_and_wait_transaction() btrfs_zoned_meta_io_lock() btrfs_write_marked_extents() btrfs_check_meta_write_pointer() btree_writepages() check_bg_is_active() [treelog_bg] btrfs_zoned_meta_io_lock() btrfs_zone_finish_one_bg() <blocks on zoned_meta_io_lock, btrfs_zone_finish() held by Task A> do_zone_finish() btrfs_inc_block_group_ro() btrfs_wait_for_commit() <blocks waiting for commit of transaction T, done by Task B> The sibling branch in check_bg_is_active() already drops zoned_meta_io_lock around do_zone_finish() for this exact reason. Do the same in the tree-log branch: release the lock around btrfs_zone_finish_one_bg() and re-acquire it afterwards. The lock only protects fs_info->active_{meta,system}_bg, which this branch does not touch, and ctx->zoned_bg keeps a reference to the block group across the unlock, so nothing is lost while the lock is dropped. This hang occasionally reproduces with fstests generic/475 on a zoned btrfs filesystem.

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 6.5.5 <6.6; patch: 0; patch: 6.12.103; 13bb483d32abb6f8ebd40141d87eb68f11cc2dd2 <c3320873e0c04ce7b746fc8fe948f07bbbbdec33; fca3a1cd3ba47f1815e0c0fcdc9aafaf02ee0a75; patch: 6.6.151; 13bb483d32abb6f8ebd40141d87eb68f11cc2dd2 <75859a7cd77cd2ddaddbcb963e3fcd34738953af; 13bb483d32abb6f8ebd40141d87eb68f11cc2dd2 <deddd28fd83c264ee2ff5cd6b34449a9f1be6112; patch: 7.2; patch: 7.1.8; 13bb483d32abb6f8ebd40141d87eb68f11cc2dd2 <1ebe51c29fa9755d5b2fea28727c051117907cf8; patch: 6.18.44; 6.6; 13bb483d32abb6f8ebd40141d87eb68f11cc2dd2 <18577e77c2c8adaadf1f7c6e9bcd1c0b14e5dcdd

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

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.