CVE-2026-97968: Software Security Vulnerability Vulnerability
UNKNOWNCVE-2026-97968 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-97968 at a Glance
How to Fix CVE-2026-97968
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-97968, 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-97968?
Which Software versions are affected?
What version fixes CVE-2026-97968?
What CWE is associated with CVE-2026-97968?
How can I check Maven dependencies for CVE-2026-97968?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-fqg8-p65w-8fh2",
"modified" : "2026-09-25T12:31:30Z",
"published" : "2026-09-25T12:31:30Z",
"aliases" : [ "CVE-2026-97968" ],
"details" : "In the Linux kernel, the following vulnerability has been resolved:\n\nhwmon: (corsair-cpro) Create debugfs entries after hwmon registration\n\nccp_debugfs_init() registers debugfs files whose private data is the devm\nallocated ccp. It runs before hwmon_device_register_with_info(), so when\nthat registration fails, ccp_probe() returns with the files still in\nplace. The HID core then frees ccp, and ccp_remove() is not called for a\nfailed probe, so nothing removes them later either. Reading one of the\nfiles dereferences the freed pointer.\n\nCreate the debugfs entries only after the hwmon device has been\nregistered, so no failing path can leave them behind.\n\nThe two version queries stay where they are. They send USB commands\nwithout holding ccp->mutex, which is only safe as long as nothing else\ncan call send_usb_cmd(); once the hwmon device is registered its\ncallbacks can do so concurrently. Only the debugfs creation moves, and\nit is told which queries succeeded.",
"severity" : [ ],
"affected" : [ ],
"references" : [ {
"type" : "ADVISORY",
"url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-97968"
}, {
"type" : "WEB",
"url" : "https://git.kernel.org/stable/c/508baf1713f32f287bfb4f85d759403ec8ba35a3"
}, {
"type" : "WEB",
"url" : "https://git.kernel.org/stable/c/6c5d333216a937044acd3336e9ec7e30ff2eaee4"
}, {
"type" : "WEB",
"url" : "https://git.kernel.org/stable/c/a58a966a440071bb877ef62535d1016952f83101"
}, {
"type" : "WEB",
"url" : "https://git.kernel.org/stable/c/fdfe17cb865715aad30328678344eb79889207ab"
} ],
"database_specific" : {
"cwe_ids" : [ ],
"severity" : null,
"github_reviewed" : false,
"github_reviewed_at" : null,
"nvd_published_at" : "2026-09-25T11:17:24Z"
}
}