CVE-2026-74572
btrfs: zoned: fix deadlock between metadata writeback and transaction commit
Reported by linux · Published August 15, 2026
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.
Fixed versions
Upgrade to a fixed version or later. Language registries are listed first, then Linux distributions, then vendor products.
| Package | Ecosystem | Fixed in |
|---|---|---|
| microvm-kernel6.18 | Amazon Linux | 1:6.18.44-99.149.amzn2023 |
| kernel-livepatch-6.18.44-99.149 | Amazon Linux | 1:1.0-0.amzn2023 |
| kernel6.12-modules-extra | Amazon Linux | 1:6.12.103-127.188.amzn2023 |
| perf6.18 | Amazon Linux | 1:6.18.44-99.149.amzn2023 |
| kernel6.18 | Amazon Linux | 1:6.18.44-99.149.amzn2023 |
| perf6.12 | Amazon Linux | 1:6.12.103-127.188.amzn2023 |
| kernel6.12 | Amazon Linux | 1:6.12.103-127.188.amzn2023 |
| kernel6.18-tools | Amazon Linux | 1:6.18.44-99.149.amzn2023 |
| bpftool6.18 | Amazon Linux | 1:6.18.44-99.149.amzn2023 |
| kernel6.12-headers | Amazon Linux | 1:6.12.103-127.188.amzn2023 |
| kernel6.18-modules-extra-common | Amazon Linux | 1:6.18.44-99.149.amzn2023 |
| kernel6.18-devel | Amazon Linux | 1:6.18.44-99.149.amzn2023 |
5 more packages have a fixed version. See every fix in Lookup.
Risk scores
Affected products
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | 13bb483d32abb6f8ebd40141d87eb68f11cc2dd2, 13bb483d32abb6f8ebd40141d87eb68f11cc2dd2, 13bb483d32abb6f8ebd40141d87eb68f11cc2dd2 |
| Linux | Linux | 6.6, 0, 6.6.151 |
| amazon:2023 | microvm-kernel6.18 | 0 |
| amazon:2023 | kernel-livepatch-6.18.44-99.149 | 0 |
| amazon:2023 | kernel6.12-modules-extra | 0 |
| amazon:2023 | perf6.18 | 0 |
| amazon:2023 | kernel6.18 | 0 |
| amazon:2023 | perf6.12 | 0 |
| amazon:2023 | kernel6.12 | 0 |
| amazon:2023 | kernel6.18-tools | 0 |
| amazon:2023 | bpftool6.18 | 0 |
| amazon:2023 | kernel6.12-headers | 0 |
| amazon:2023 | kernel6.18-modules-extra-common | 0 |
| amazon:2023 | kernel6.18-devel | 0 |
| amazon:2023 | bpftool6.12 | 0 |
| amazon:2023 | python3-perf6.18 | 0 |
| amazon:2023 | kernel-livepatch-6.12.103-127.188 | 0 |
| amazon:2023 | python3-perf6.12 | 0 |
| Linux | Linux | 7.2, *, 13bb483d32abb6f8ebd40141d87eb68f11cc2dd2 |
| amazon:2023 | kernel6.18-tools-devel | 0 |
…and 7 more
Timeline
- Aug 15, 2026 CVE Published
- Aug 16, 2026 EPSS Score (30 in total, the first dated here)
- Aug 19, 2026 Security Advisory
- Oct 16, 2026 CVE Updated
Query this with the API
The same record, from the CLI:
vulnetix vdb vuln CVE-2026-74572
vulnetix vdb fixes CVE-2026-74572
Or with curl, using the org id and key from your account page:
curl -s -H "Authorization: ApiKey ${VULNETIX_ORG_ID}:${VULNETIX_API_KEY}" \
"https://api.vdb.vulnetix.com/v2/vuln/CVE-2026-74572/fixes/registry"
The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart