{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-97975 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-97975 is a vulnerability in Linux, published on 25 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-97975 and fix it if it is affected.\n\nWhat it is: CVE-2026-97975 is a vulnerability in Linux, published on 25 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-97975 in the wild and no public exploit code.\n\nAffected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-97975/ (Markdown: https://insights.sbomify.com/CVE-2026-97975/index.md)","id":"CVE-2026-97975","markdown":"https://insights.sbomify.com/CVE-2026-97975/index.md","name":"CVE-2026-97975","record":{"aliases":["AZL-104654","BELL-CVE-2026-97975","DEBIAN-CVE-2026-97975","GHSA-2vfm-8xc8-7w2c","UBUNTU-CVE-2026-97975"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel Bluetooth","requires_auth":"low_privilege","summary":"A race condition in the Linux kernel Bluetooth subsystem causes a NULL pointer dereference, leading to a system crash.","user_interaction":"not_required","vuln_class":"null_dereference"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"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(\u0026dev-\u003ep-\u003eknode_parent) using the stale parent snapshot, causing\nklist_put() to dereference knode_klist(n)-\u003eput 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-\u003edev outlived its parent hdev-\u003edev when child devices held\nreferences to conn-\u003edev, because conn-\u003edev only held a reference to\nhdev-\u003edev while registered in sysfs.\n\nFix the issue properly by taking an explicit reference to the parent device\nwith get_device(\u0026hdev-\u003edev) 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-\u003edev remains valid for the entire lifecycle of conn-\u003edev,\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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Bluetooth: hci_sysfs: Fix NULL pointer dereference in device_del()","id":"CVE-2026-97975","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"null_dereference","year":"2026"},"n_packages":0,"n_references":5,"next":{"headline":"Bluetooth: btintel_pcie: validate packet_len before skb_put_data","id":"CVE-2026-97976"},"packages":[],"prev":{"headline":"ipv6: null-check fib6_node before accessing in __ip6_del_rt_siblings()","id":"CVE-2026-97974"},"products":["Linux"],"published":"2026-09-25","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-10-21","vendors":["Linux"]},"summary":"A race condition in the Linux kernel Bluetooth subsystem causes a NULL pointer dereference, leading to a system crash.","url":"https://insights.sbomify.com/CVE-2026-97975/"}