CVE-2026-72080: Software Security Vulnerability Vulnerability
HIGHCVE-2026-72080 is a HIGH (CVSS 7.8) security vulnerability vulnerability (CWE-416: Use After Free) affecting Software libraries in the Maven ecosystem. The weakness occurs when the product reuses or references memory after it has been freed. at some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. any operations using the original pointer are no longer valid because the memory "belongs" to the code that operates on the new pointer.. Remediation is available in the latest vendor maintenance releases.
CVE-2026-72080 at a Glance
Security Impact
CVSS: 7.8
The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H).
How to Fix CVE-2026-72080
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-72080, 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 CWE-416: Use After Free, where the product reuses or references memory after it has been freed. at some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. any operations using the original pointer are no longer valid because the memory "belongs" to the code that operates on the new pointer. 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-72080?
Which Software versions are affected?
What version fixes CVE-2026-72080?
What is the CVSS score of CVE-2026-72080?
What CWE is associated with CVE-2026-72080?
How can I check Maven dependencies for CVE-2026-72080?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-3mx4-vrgg-r9xh",
"modified" : "2026-08-17T06:33:08Z",
"published" : "2026-08-15T06:32:11Z",
"aliases" : [ "CVE-2026-72080" ],
"details" : "In the Linux kernel, the following vulnerability has been resolved:\n\nfs/resctrl: Fix use-after-free during unmount\n\nDuring unmount or failure teardown all mon_data structures that contain\nmonitoring event file private data are freed after which kernfs nodes are\nremoved. However, the RDT_DELETED flag is never set for the statically\nallocated default resource group.\n\nA concurrent reader of an event file associated with the default resource\ngroup may, after dropping kernfs active protection, block on rdtgroup_mutex\nwhile unmount proceeds to free the file private data and destroy the kernfs\nnode without waiting for the reader.\n\nWhen the mutex is released, the reader wakes up, observes that RDT_DELETED\nis not set for the default group, and dereferences the already-freed\nfile private data.\n\nThe scenario can be depicted as follows:\n CPU0 CPU1\n /*\n * Default resource group's\n * monitoring data accessible via\n * kernfs file with kernfs_node::priv\n * pointing to a struct mon_data.\n * User opens the file for reading.\n */\n rdtgroup_mondata_show() /* arch encounters fatal error */\n rdtgroup_kn_lock_live() resctrl_exit()\n atomic_inc(&rdtgroup_default.waitcount) cpus_read_lock()\n kernfs_break_active_protection(kn) mutex_lock(&rdtgroup_mutex)\n cpus_read_lock() resctrl_fs_teardown()\n mutex_lock(&rdtgroup_mutex) rmdir_all_sub()\n mon_put_kn_priv()\n /* Delete all mon_data structures */\n rdtgroup_destroy_root()\n kernfs_destroy_root()\n rdtgroup_default.kn = NULL\n mutex_unlock(&rdtgroup_mutex)\n /*\n * rdtgroup_default.flags is empty so\n * rdtgroup_kn_lock_live() returns\n * &rdtgroup_default\n */\n md = of->kn->priv;\n\n /* md points to freed mon_data */\n\nSet RDT_DELETED for the default group unconditionally since the flag does\nnot lead to the freeing of this statically allocated group.\n\nDo not allow a new resctrl mount if there are any waiters on default group\nof previous mount. A new mount will re-initialize the default group that\nwould appear to waiters from previous mount as though the default group is\naccessible causing them to access the mon_data structures from the previous\nmount that have been removed.",
"severity" : [ {
"type" : "CVSS_V3",
"score" : "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H"
} ],
"affected" : [ ],
"references" : [ {
"type" : "ADVISORY",
"url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-72080"
}, {
"type" : "WEB",
"url" : "https://git.kernel.org/stable/c/52fce648607e0d6a76eeb443d78708c49df1c554"
}, {
"type" : "WEB",
"url" : "https://git.kernel.org/stable/c/7b7bb07efe41bb646a93c4624aa2bb35df190342"
}, {
"type" : "WEB",
"url" : "https://git.kernel.org/stable/c/7d330a1d663381579b9d5dafa642b1b3158a0ce2"
} ],
"database_specific" : {
"cwe_ids" : [ "CWE-416" ],
"severity" : "HIGH",
"github_reviewed" : false,
"github_reviewed_at" : null,
"nvd_published_at" : "2026-08-15T06:21:18Z"
}
}