{
  "affected": [
    {
      "ecosystem_specific": {
        "urgency": "not yet assigned"
      },
      "package": {
        "ecosystem": "Debian:13",
        "name": "linux"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "6.12.105-1"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    },
    {
      "ecosystem_specific": {
        "urgency": "not yet assigned"
      },
      "package": {
        "ecosystem": "Debian:14",
        "name": "linux"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "7.1.8-1"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    },
    {
      "ecosystem_specific": {
        "urgency": "not yet assigned"
      },
      "package": {
        "ecosystem": "Debian:12",
        "name": "linux-6.12"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "6.12.107-1~deb12u1"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "details": "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-\u003ezoned_meta_io_lock across the whole writeback loop, including the call to btrfs_check_meta_write_pointer() -\u003e 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()               \u003cblocks on zoned_meta_io_lock,        btrfs_zone_finish()                      held by Task A\u003e         do_zone_finish()          btrfs_inc_block_group_ro()           btrfs_wait_for_commit()            \u003cblocks waiting for commit             of transaction T, done by             Task B\u003e  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-\u003eactive_{meta,system}_bg, which this branch does not touch, and ctx-\u003ezoned_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.",
  "id": "DEBIAN-CVE-2026-74572",
  "modified": "2026-09-19T21:47:22.588165251Z",
  "published": "2026-08-15T13:18:02.837Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://security-tracker.debian.org/tracker/CVE-2026-74572"
    }
  ],
  "severity": [
    {
      "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
      "type": "CVSS_V3"
    }
  ],
  "upstream": [
    "CVE-2026-74572"
  ]
}