CVE-2026-97975: Software Security Vulnerability Vulnerability
UNKNOWNCVE-2026-97975 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-97975 at a Glance
How to Fix CVE-2026-97975
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-97975, 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-97975?
Which Software versions are affected?
What version fixes CVE-2026-97975?
What CWE is associated with CVE-2026-97975?
How can I check Maven dependencies for CVE-2026-97975?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-2vfm-8xc8-7w2c",
"modified" : "2026-09-25T12:31:31Z",
"published" : "2026-09-25T12:31:31Z",
"aliases" : [ "CVE-2026-97975" ],
"details" : "In the Linux kernel, the following vulnerability has been resolved:\n\nBluetooth: hci_sysfs: Fix NULL pointer dereference in device_del()\n\nA NULL pointer dereference in klist_put() occurs when a child device (such\nas a BNEP network device in bnep_session) is concurrently being\nunregistered while hci_conn_del_sysfs() reparents child devices.\n\nThis is caused by a race condition between hci_conn_del_sysfs() and\nconcurrent child device unregistration (e.g. bnep_session calling\nunregister_netdev()). During device unregistration, device_del() snapshots\na non-NULL parent pointer. Concurrently, hci_conn_del_sysfs() finds the\nchild device using device_find_any_child() and calls device_move() to\nreparent it to NULL, which removes the node from its parent's klist and\nclears knode_parent. Subsequently, device_del() calls\nklist_del(&dev->p->knode_parent) using the stale parent snapshot, causing\nklist_put() to dereference knode_klist(n)->put on an already removed node,\nresulting in a NULL pointer dereference.\n\nThis race was introduced by commit 27aabf27fd01 (\"Bluetooth: fix\nuse-after-free in device_for_each_child()\"), which replaced\ndevice_find_child(..., __match_tty) with device_find_any_child() in\nhci_conn_del_sysfs(). That change was intended to avoid a use-after-free\nwhere conn->dev outlived its parent hdev->dev when child devices held\nreferences to conn->dev, because conn->dev only held a reference to\nhdev->dev while registered in sysfs.\n\nFix the issue properly by taking an explicit reference to the parent device\nwith get_device(&hdev->dev) in hci_conn_init_sysfs() and dropping it with\nput_device(parent) in bt_link_release() when the conn device is freed. This\nensures that hdev->dev remains valid for the entire lifecycle of conn->dev,\nresolving the underlying use-after-free. With the parent reference held\nproperly, restore the __match_tty filter in hci_conn_del_sysfs() so that\ndevice_move() is only invoked on persistent RFCOMM TTY devices as\noriginally intended, eliminating the race condition with unregistering\nnetwork devices.",
"severity" : [ ],
"affected" : [ ],
"references" : [ {
"type" : "ADVISORY",
"url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-97975"
}, {
"type" : "WEB",
"url" : "https://git.kernel.org/stable/c/9b851b09b392da68bd715601f10a5adb2d8d19b8"
}, {
"type" : "WEB",
"url" : "https://git.kernel.org/stable/c/9e9ece97b8e716890793de261574b8efef7d8702"
}, {
"type" : "WEB",
"url" : "https://git.kernel.org/stable/c/eeabdb25c3209569367e99a85ca9a503b64a646d"
} ],
"database_specific" : {
"cwe_ids" : [ ],
"severity" : null,
"github_reviewed" : false,
"github_reviewed_at" : null,
"nvd_published_at" : "2026-09-25T11:17:25Z"
}
}