{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-74572 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-74572 is a high-severity vulnerability in Linux, published on 15 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-74572 and fix it if it is affected.\n\nWhat it is: CVE-2026-74572 is a high-severity vulnerability in Linux, published on 15 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-74572 in the wild and no public exploit code.\n\nAffected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-74572/ (Markdown: https://insights.sbomify.com/CVE-2026-74572/index.md)","id":"CVE-2026-74572","markdown":"https://insights.sbomify.com/CVE-2026-74572/index.md","name":"CVE-2026-74572","record":{"aliases":["AZL-96141","BELL-CVE-2026-74572","DEBIAN-CVE-2026-74572","GHSA-623q-h292-q6ff","UBUNTU-CVE-2026-74572"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":true,"product_category":"Linux kernel","requires_auth":"none","summary":"A deadlock in the Linux kernel's btrfs zoned filesystem can cause a denial of service during metadata writeback and transaction commits.","user_interaction":"not_required","vuln_class":"race_condition"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":7.5,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","version":"3.1"},"cwes":[],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\nbtrfs: zoned: fix deadlock between metadata writeback and transaction commit\n\nWhen writing out metadata extent buffers in a zoned filesystem,\nbtree_writepages() holds fs_info-\u003ezoned_meta_io_lock across the whole\nwriteback loop, including the call to btrfs_check_meta_write_pointer() -\u003e\ncheck_bg_is_active().\n\nFor the tree-log block group, check_bg_is_active() may fail to activate\nthe zone and fall back to btrfs_zone_finish_one_bg() to free an active\nzone. That path waits for the running transaction to commit while still\nholding zoned_meta_io_lock, but the committer needs that same lock to\nwrite out the tree extents, so the two tasks deadlock:\n\n  Task A (kworker, metadata writeback)      Task B (fsstress, transaction commit)\n  ------------------------------------      -------------------------------------\n  wb_workfn()                               btrfs_commit_transaction(T)\n   btree_writepages()                        btrfs_write_and_wait_transaction()\n    btrfs_zoned_meta_io_lock()                btrfs_write_marked_extents()\n    btrfs_check_meta_write_pointer()           btree_writepages()\n     check_bg_is_active() [treelog_bg]          btrfs_zoned_meta_io_lock()\n      btrfs_zone_finish_one_bg()               \u003cblocks on zoned_meta_io_lock,\n       btrfs_zone_finish()                      held by Task A\u003e\n        do_zone_finish()\n         btrfs_inc_block_group_ro()\n          btrfs_wait_for_commit()\n           \u003cblocks waiting for commit\n            of transaction T, done by\n            Task B\u003e\n\nThe sibling branch in check_bg_is_active() already drops zoned_meta_io_lock\naround do_zone_finish() for this exact reason. Do the same in the tree-log\nbranch: release the lock around btrfs_zone_finish_one_bg() and re-acquire\nit afterwards. The lock only protects fs_info-\u003eactive_{meta,system}_bg,\nwhich this branch does not touch, and ctx-\u003ezoned_bg keeps a reference to\nthe block group across the unlock, so nothing is lost while the lock\nis dropped.\n\nThis hang occasionally reproduces with fstests generic/475 on a zoned\nbtrfs filesystem.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"btrfs: zoned: fix deadlock between metadata writeback and transaction commit","id":"CVE-2026-74572","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"race_condition","year":"2026"},"n_packages":0,"n_references":5,"next":{"headline":"iommu/arm-smmu-v3-iommufd: Require exactly one Stream ID for a vDEVICE","id":"CVE-2026-74573"},"packages":[],"prev":{"headline":"btrfs: skip global block reserve accounting for rescue mounts","id":"CVE-2026-74571"},"products":["Linux"],"published":"2026-08-15","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-10-16","vendors":["Linux"]},"summary":"A deadlock in the Linux kernel's btrfs zoned filesystem can cause a denial of service during metadata writeback and transaction commits.","url":"https://insights.sbomify.com/CVE-2026-74572/"}