CVE-2026-72292: Software Security Vulnerability Vulnerability
UNKNOWNCVE-2026-72292 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-72292 at a Glance
How to Fix CVE-2026-72292
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.
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-72292, 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
References
Frequently Asked Questions
What is CVE-2026-72292?
Which Software versions are affected?
What version fixes CVE-2026-72292?
What CWE is associated with CVE-2026-72292?
How can I check Maven dependencies for CVE-2026-72292?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-g39r-65h4-wx32",
"modified" : "2026-08-15T06:32:18Z",
"published" : "2026-08-15T06:32:18Z",
"aliases" : [ "CVE-2026-72292" ],
"details" : "In the Linux kernel, the following vulnerability has been resolved:\n\nKVM: s390: Initialize KVM_S390_GET_CMMA_BITS memory\n\nkvm_s390_get_cmma_bits() allocates its output buffer with vmalloc(),\nwhich does not zero the returned pages:\n\n\tvalues = vmalloc(args->count);\n\nIn the non-peek (migration) path, dat_get_cmma() reports a byte count\nspanning from the first to the last dirty page, but __dat_get_cmma_pte()\nwrites values[gfn - start] only for pages whose CMMA dirty bit is set.\nThe walk uses DAT_WALK_IGN_HOLES, so clean and unmapped pages that lie\nbetween two dirty pages within the reported span are visited but never\nstore their byte. Those gaps (up to KVM_S390_MAX_BIT_DISTANCE pages\neach) stay uninitialized yet fall inside [0, count) and are copied out\nby copy_to_user(), disclosing stale kernel memory to user space.\n\nBefore the switch to the new gmap implementation the buffer was fully\npopulated for every gfn in the span, so no uninitialized bytes were\nexposed; the dirty-only walk introduced the leak.\n\nUse vzalloc() so the gaps read back as zero.",
"severity" : [ ],
"affected" : [ ],
"references" : [ {
"type" : "ADVISORY",
"url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-72292"
}, {
"type" : "WEB",
"url" : "https://git.kernel.org/stable/c/a4a19941ccb2164edc3491faa5ac5df82e94b363"
}, {
"type" : "WEB",
"url" : "https://git.kernel.org/stable/c/c7dda3d0f869dc97223448a06c9a2e5235928e48"
} ],
"database_specific" : {
"cwe_ids" : [ ],
"severity" : null,
"github_reviewed" : false,
"github_reviewed_at" : null,
"nvd_published_at" : "2026-08-15T06:22:01Z"
}
}