CVE-2026-97920: Software Security Vulnerability Vulnerability
UNKNOWNCVE-2026-97920 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-97920 at a Glance
How to Fix CVE-2026-97920
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-97920, 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-97920?
Which Software versions are affected?
What version fixes CVE-2026-97920?
What CWE is associated with CVE-2026-97920?
How can I check Maven dependencies for CVE-2026-97920?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-r69x-p84r-2wc9",
"modified" : "2026-10-03T12:31:20Z",
"published" : "2026-09-25T12:31:28Z",
"aliases" : [ "CVE-2026-97920" ],
"details" : "In the Linux kernel, the following vulnerability has been resolved:\n\ntracing: Keep the entry count when the histogram stats allocation fails\n\nprint_entries() uses n_entries both as the number of sort entries and as\nits own return value, so the -ENOMEM it stores when the stats allocation\nfails overwrites the count that the cleanup still needs:\n\n\tn_entries = tracing_map_sort_entries(map, ...);\n\tif (n_entries < 0)\n\t\treturn n_entries;\n\t...\n\t\t\tif (!stats) {\n\t\t\t\tn_entries = -ENOMEM;\n\t\t\t\tgoto out;\n\t\t\t}\n\t...\n out:\n\ttracing_map_destroy_sort_entries(sort_entries, n_entries);\n\ntracing_map_destroy_sort_entries() takes an unsigned int and loops up to\nit, so -ENOMEM arrives as 4294967284. It walks an array of at most\nmap->max_elts pointers and calls destroy_sort_entry(), which dereferences\nand frees, on whatever lies past the end.\n\nReading the hist file of a trigger with a .percent value, with that\nallocation forced to fail:\n\n BUG: KASAN: vmalloc-out-of-bounds in tracing_map_destroy_sort_entries+0xa0/0xb0\n Read of size 8 at addr ffffc90000045000 by task init/1\n tracing_map_destroy_sort_entries+0xa0/0xb0\n hist_show+0x6f7/0x1df0\n seq_read_iter+0x2b8/0x1190\n vfs_read+0x176/0xa40\n The buggy address belongs to a 4-page vmalloc region starting at\n ffffc90000041000 allocated at tracing_map_sort_entries+0x5c/0xd50\n\nA few pages further the fault is fatal. The registers at the oops confirm\nthe bound: the loop's end pointer less the array start, over the pointer\nsize, is 4294967284.\n\nReturn the error in a separate variable and leave n_entries holding the\ncount, the way tracing_map_sort_entries() does on its own error path.\n\nThe stats block is only entered for a value carrying .percent or .graph,\nwhich __create_val_field() has rejected since v6.3, so this cannot be\nreached in mainline as it stands. It becomes reachable again with\n\"tracing: hist: let values keep the percent and graph modifiers\", so it\nshould be applied first.",
"severity" : [ ],
"affected" : [ ],
"references" : [ {
"type" : "ADVISORY",
"url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-97920"
}, {
"type" : "WEB",
"url" : "https://git.kernel.org/stable/c/06f5634ec5584954177f9a22e36b3bfb398a971b"
}, {
"type" : "WEB",
"url" : "https://git.kernel.org/stable/c/17e87ce55f877efff1b08fe509e8bf91378cbbc9"
}, {
"type" : "WEB",
"url" : "https://git.kernel.org/stable/c/89c978d67ad01ce28223944cc58e95feea177b35"
}, {
"type" : "WEB",
"url" : "https://git.kernel.org/stable/c/9bd8321f5370295d1ae96dd17d43be3c9edd441b"
}, {
"type" : "WEB",
"url" : "https://git.kernel.org/stable/c/c80b2a8067d58ff7d268ceef781c68b37a16c321"
}, {
"type" : "WEB",
"url" : "https://git.kernel.org/stable/c/fe05eeed27128e17d38dbc0af02e4470bcecda89"
} ],
"database_specific" : {
"cwe_ids" : [ ],
"severity" : null,
"github_reviewed" : false,
"github_reviewed_at" : null,
"nvd_published_at" : "2026-09-25T11:17:19Z"
}
}