CVE-2026-72359: Software Security Vulnerability Vulnerability
UNKNOWNCVE-2026-72359 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-72359 at a Glance
How to Fix CVE-2026-72359
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-72359, 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-72359?
Which Software versions are affected?
What version fixes CVE-2026-72359?
What CWE is associated with CVE-2026-72359?
How can I check Maven dependencies for CVE-2026-72359?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-r35w-2gcj-cx97",
"modified" : "2026-08-15T06:32:21Z",
"published" : "2026-08-15T06:32:21Z",
"aliases" : [ "CVE-2026-72359" ],
"details" : "In the Linux kernel, the following vulnerability has been resolved:\n\ndrm/xe: fix NPD in bo_meminfo()\n\nWhen a buffer object is purged, its ttm.resource is set to NULL via the\nTTM pipeline gutting flow. However, the BO remains in the client's\nobject list until userspace explicitly closes the GEM handle. If memory\nstats are queried during this time, accessing bo->ttm.resource->mem_type\nwill result in a NULL pointer dereference.\n\nFix this by safely skipping purged BOs in bo_meminfo, as they no longer\nconsume any memory.\n\nUser is getting NPD on device resume, and possible theory is that in\nbo_move(), if we need to evict something to SYSTEM to save the CCS state,\nbut the BO is marked as dontneed, this won't trigger a move but will\nnuke the pages, leaving us with a NULL bo resource. And the meminfo()\ndoesn't look ready to handle a NULL resource.\n\nv2 (Sashiko):\n - There could potentially be other cases where we might end up with a\n NULL resource, so make this a general NULL check for now.\n\n(cherry picked from commit c9a8e7daa0afe3161111e27fd92176e608c7f186)",
"severity" : [ ],
"affected" : [ ],
"references" : [ {
"type" : "ADVISORY",
"url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-72359"
}, {
"type" : "WEB",
"url" : "https://git.kernel.org/stable/c/5ff2212f0e0779b0b0cbf91fbf970144107c4257"
}, {
"type" : "WEB",
"url" : "https://git.kernel.org/stable/c/b5c55015d4164a0f206bcdcf2985da948b3c7837"
} ],
"database_specific" : {
"cwe_ids" : [ ],
"severity" : null,
"github_reviewed" : false,
"github_reviewed_at" : null,
"nvd_published_at" : "2026-08-15T06:22:09Z"
}
}