CVE-2026-74472: Software Security Vulnerability Vulnerability

UNKNOWN
Advisory Identifier: GHSA-7jg9-vhj9-wg56
Share
Published
Advisory Summary

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

CVE-2026-74472 at a Glance

CVE Identifier CVE-2026-74472
GHSA Identifier GHSA-7jg9-vhj9-wg56
Severity N/A
CVSS v3.1 Base Score N/A
CWE Classification General Security Weakness
Affected Product Software
Package Ecosystem Maven
Published Date
Last Updated

How to Fix CVE-2026-74472

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-74472, 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: ublk: reset kernel-owned dev_info fields in ublk_ctrl_add_dev() ublk_ctrl_add_dev() memcpy()s the userspace ublksrv_ctrl_dev_info into ub->dev_info and then fixes up the fields the driver owns, but misses ->state and ->ublksrv_pid. A device added with ->state = UBLK_S_DEV_LIVE passes the "->state != UBLK_S_DEV_DEAD" test that ublk_stop_dev_unlocked() uses as its proxy for "a disk is attached", while ->ub_disk is still NULL, so DEL_DEV right after ADD_DEV oopses in del_gendisk(). UBLK_S_DEV_QUIESCED plus UBLK_F_USER_RECOVERY dies one step earlier, in ublk_force_abort_dev(). A poisoned ->state also gets START_USER_RECOVERY and the char device read/write path onto a device that was never started, and wedges START_DEV at -EEXIST. A poisoned ->ublksrv_pid just makes GET_DEV_INFO report an unrelated task as the ublk server. Reset both after the memcpy(), as ublk_detach_disk() does. Userspace only ever reads these back, so correcting them silently breaks nothing. ADD_DEV has copied ->state in unsanitized since ublk was merged, but back then it was harmless: the gendisk was allocated during ADD_DEV, and both teardown and the START_DEV -EEXIST check keyed off disk_live() rather than ->state. The oops became reachable once the disk allocation moved to START_DEV and those checks switched to ->state.

References

NVD — CVE-2026-74472 NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-74472
git.kernel.org/stable/c/127033b793... WEB
https://git.kernel.org/stable/c/127033b79383a3e78361d7e971588aa8849f5124
git.kernel.org/stable/c/205feb72e5... WEB
https://git.kernel.org/stable/c/205feb72e5beb3140e4e1403b6cff30cf739bab9
git.kernel.org/stable/c/787c944502... WEB
https://git.kernel.org/stable/c/787c944502e7e63d20a9201bada77e0dd924f458
git.kernel.org/stable/c/b67ce16b26... WEB
https://git.kernel.org/stable/c/b67ce16b26ad0f14cfd6071013840aa95f823bea
git.kernel.org/stable/c/e65848e4ce... WEB
https://git.kernel.org/stable/c/e65848e4ce352bac9e3465099354c8b8f845391f
git.kernel.org/stable/c/ee41b00858... WEB
https://git.kernel.org/stable/c/ee41b00858ca65b4428e99efe39a4277c1f043d2

Frequently Asked Questions

What is CVE-2026-74472?
CVE-2026-74472 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-74472?
Upgrading to current release patches (or the latest patched release for your respective branch) resolves the vulnerability.
What CWE is associated with CVE-2026-74472?
CVE-2026-74472 is classified under General Security Weakness.
How can I check Maven dependencies for CVE-2026-74472?
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-7jg9-vhj9-wg56",
  "modified" : "2026-08-19T18:32:28Z",
  "published" : "2026-08-15T15:30:33Z",
  "aliases" : [ "CVE-2026-74472" ],
  "details" : "In the Linux kernel, the following vulnerability has been resolved:\n\nublk: reset kernel-owned dev_info fields in ublk_ctrl_add_dev()\n\nublk_ctrl_add_dev() memcpy()s the userspace ublksrv_ctrl_dev_info into\nub->dev_info and then fixes up the fields the driver owns, but misses\n->state and ->ublksrv_pid.\n\nA device added with ->state = UBLK_S_DEV_LIVE passes the\n\"->state != UBLK_S_DEV_DEAD\" test that ublk_stop_dev_unlocked() uses as its\nproxy for \"a disk is attached\", while ->ub_disk is still NULL, so DEL_DEV\nright after ADD_DEV oopses in del_gendisk().  UBLK_S_DEV_QUIESCED plus\nUBLK_F_USER_RECOVERY dies one step earlier, in ublk_force_abort_dev().  A\npoisoned ->state also gets START_USER_RECOVERY and the char device\nread/write path onto a device that was never started, and wedges START_DEV\nat -EEXIST.  A poisoned ->ublksrv_pid just makes GET_DEV_INFO report an\nunrelated task as the ublk server.\n\nReset both after the memcpy(), as ublk_detach_disk() does.  Userspace only\never reads these back, so correcting them silently breaks nothing.\n\nADD_DEV has copied ->state in unsanitized since ublk was merged, but back\nthen it was harmless: the gendisk was allocated during ADD_DEV, and both\nteardown and the START_DEV -EEXIST check keyed off disk_live() rather than\n->state.  The oops became reachable once the disk allocation moved to\nSTART_DEV and those checks switched to ->state.",
  "severity" : [ ],
  "affected" : [ ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-74472"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/127033b79383a3e78361d7e971588aa8849f5124"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/205feb72e5beb3140e4e1403b6cff30cf739bab9"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/787c944502e7e63d20a9201bada77e0dd924f458"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/b67ce16b26ad0f14cfd6071013840aa95f823bea"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/e65848e4ce352bac9e3465099354c8b8f845391f"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/ee41b00858ca65b4428e99efe39a4277c1f043d2"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : null,
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-08-15T13:17:51Z"
  }
}