CVE-2026-97915: Software Security Vulnerability Vulnerability
UNKNOWNCVE-2026-97915 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-97915 at a Glance
How to Fix CVE-2026-97915
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-97915, 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-97915?
Which Software versions are affected?
What version fixes CVE-2026-97915?
What CWE is associated with CVE-2026-97915?
How can I check Maven dependencies for CVE-2026-97915?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-qr56-qc89-442x",
"modified" : "2026-09-25T12:31:28Z",
"published" : "2026-09-25T12:31:28Z",
"aliases" : [ "CVE-2026-97915" ],
"details" : "In the Linux kernel, the following vulnerability has been resolved:\n\naccel/ivpu: Limit firmware log name prints to field size\n\nThe name in struct vpu_tracing_buffer_header is a fixed-size array\npopulated by the NPU firmware. It is expected to be NUL-terminated,\nbut nothing on the host side enforces this, so printing it with an\nunbounded string conversion would read past the field if the\nterminator is ever missing and expose adjacent bytes of the shared\ntracing BO through dmesg and the debugfs FW log output.\n\nPrint at most as many characters as the name field holds, so the output\nnever runs past it even if the string is not NUL-terminated.",
"severity" : [ ],
"affected" : [ ],
"references" : [ {
"type" : "ADVISORY",
"url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-97915"
}, {
"type" : "WEB",
"url" : "https://git.kernel.org/stable/c/3d7130807009e9be6132c1394a2c7708a3ba39a7"
}, {
"type" : "WEB",
"url" : "https://git.kernel.org/stable/c/5d06257359c9006a208fece9eb7f0a0e83e0cc92"
}, {
"type" : "WEB",
"url" : "https://git.kernel.org/stable/c/6dbba89df4e842d226f5cd3dbc5e94533cfceea2"
}, {
"type" : "WEB",
"url" : "https://git.kernel.org/stable/c/95bf070f3225dc7175725438c916ad321d42fe45"
} ],
"database_specific" : {
"cwe_ids" : [ ],
"severity" : null,
"github_reviewed" : false,
"github_reviewed_at" : null,
"nvd_published_at" : "2026-09-25T11:17:18Z"
}
}