CVE-2026-74572: Software Security Vulnerability Vulnerability

HIGH
Advisory Identifier: GHSA-623q-h292-q6ff
Share
CVSS 7.5
Published
Advisory Summary

CVE-2026-74572 is a HIGH (CVSS 7.5) security vulnerability vulnerability (General Security Weakness) affecting Software libraries in the Maven ecosystem. Remediation is available in the latest vendor maintenance releases.

CVE-2026-74572 at a Glance

CVE Identifier CVE-2026-74572
GHSA Identifier GHSA-623q-h292-q6ff
Severity HIGH
CVSS v3.1 Base Score 7.5
CWE Classification General Security Weakness
Affected Product Software
Package Ecosystem Maven
Published Date
Last Updated

Security Impact

CVSS: 7.5

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required None (PR:N)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality None (C:N)
Integrity None (I:N)
Availability High (A:H)

How to Fix CVE-2026-74572

To remediate this vulnerability, upgrade all affected Software dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release: 

mvn dependency:tree

How to Check if You Are Affected

To determine whether your Java application is affected by CVE-2026-74572, inspect your build dependencies using the Maven Dependency Plugin:

mvn dependency:tree

Analyze the terminal output to locate any version of Software in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than the patched release), your application is affected.

Note: The mvn dependency:tree command inspects the resolved dependency graph declared in your project's POM files; it does not perform automated security scanning or inspect runtime dynamic classpaths. Always verify runtime container classpaths and shaded JARs.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under General Security Weakness. In Software, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

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.

References

NVD — CVE-2026-74572 NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-74572
git.kernel.org/stable/c/18577e77c2... WEB
https://git.kernel.org/stable/c/18577e77c2c8adaadf1f7c6e9bcd1c0b14e5dcdd
git.kernel.org/stable/c/1ebe51c29f... WEB
https://git.kernel.org/stable/c/1ebe51c29fa9755d5b2fea28727c051117907cf8
git.kernel.org/stable/c/75859a7cd7... WEB
https://git.kernel.org/stable/c/75859a7cd77cd2ddaddbcb963e3fcd34738953af
git.kernel.org/stable/c/c3320873e0... WEB
https://git.kernel.org/stable/c/c3320873e0c04ce7b746fc8fe948f07bbbbdec33
git.kernel.org/stable/c/deddd28fd8... WEB
https://git.kernel.org/stable/c/deddd28fd83c264ee2ff5cd6b34449a9f1be6112

Frequently Asked Questions

What is CVE-2026-74572?
CVE-2026-74572 is a security vulnerability in Software classified as a security vulnerability vulnerability under General Security Weakness.
Which Software versions are affected?
Affected versions include releases prior to current release patches.
What version fixes CVE-2026-74572?
Upgrading to current release patches (or the latest patched release for your respective branch) resolves the vulnerability.
What is the CVSS score of CVE-2026-74572?
CVE-2026-74572 has a CVSS v3.1 base score of 7.5 (HIGH) with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H.
What CWE is associated with CVE-2026-74572?
CVE-2026-74572 is classified under General Security Weakness.
How can I check Maven dependencies for CVE-2026-74572?
Run the dependency tree command: 'mvn dependency:tree'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
View Raw JSON 
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-623q-h292-q6ff",
  "modified" : "2026-08-17T06:33:54Z",
  "published" : "2026-08-15T15:30:36Z",
  "aliases" : [ "CVE-2026-74572" ],
  "details" : "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->zoned_meta_io_lock across the whole\nwriteback loop, including the call to btrfs_check_meta_write_pointer() ->\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()               <blocks on zoned_meta_io_lock,\n       btrfs_zone_finish()                      held by Task A>\n        do_zone_finish()\n         btrfs_inc_block_group_ro()\n          btrfs_wait_for_commit()\n           <blocks waiting for commit\n            of transaction T, done by\n            Task B>\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->active_{meta,system}_bg,\nwhich this branch does not touch, and ctx->zoned_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.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H"
  } ],
  "affected" : [ ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-74572"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/18577e77c2c8adaadf1f7c6e9bcd1c0b14e5dcdd"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/1ebe51c29fa9755d5b2fea28727c051117907cf8"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/75859a7cd77cd2ddaddbcb963e3fcd34738953af"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/c3320873e0c04ce7b746fc8fe948f07bbbbdec33"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/deddd28fd83c264ee2ff5cd6b34449a9f1be6112"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : "HIGH",
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-08-15T13:18:02Z"
  }
}