Kernel crash via Bluetooth device reparenting race
Published Sep 25, 2026 · Updated Sep 25, 2026
Race condition in Linux kernel Bluetooth HCI sysfs code allows attackers to crash the kernel via concurrent child-device teardown. The race lets device_del use a stale parent snapshot after hci_conn_del_sysfs moves the child and clears knode_parent, causing klist_put to dereference NULL. Reachability requires Bluetooth child-device unregistration to overlap connection-device reparenting; the bounded consequence is a kernel crash.
Summary
What happened
Race condition in Linux kernel Bluetooth HCI sysfs code allows attackers to crash the kernel via concurrent child-device teardown. The race lets device_del use a stale parent snapshot after hci_conn_del_sysfs moves the child and clears knode_parent, causing klist_put to dereference NULL. Reachability requires Bluetooth child-device unregistration to overlap connection-device reparenting; the bounded consequence is a kernel crash.
The record
- CVE
- CVE-2026-97975
- Published
- Sep 25, 2026
- Updated
- Sep 25, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- T1499
- Attack vector
- Unavailable
- Privileges
- Unavailable
Timeline
How it unfolded
- Sep 25, 2026CVE publishedPublication date reported by the CVE source.
- Sep 25, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0f67ca2a80acf8b207240405b7f72d660665d3df
- Affected versionversion=27aabf27fd014ae037cc179c61b0bee7cff55b3d <9b851b09b392da68bd715601f10a5adb2d8d19b8
- Affected versionversion=27aabf27fd014ae037cc179c61b0bee7cff55b3d <9e9ece97b8e716890793de261574b8efef7d8702
- Affected versionversion=27aabf27fd014ae037cc179c61b0bee7cff55b3d <eeabdb25c3209569367e99a85ca9a503b64a646d
- Affected versionversion=5.10.231 <5.11
- Affected versionversion=5.15.174 <5.16
- Affected versionversion=5.4.297 <5.5
- Affected versionversion=6.11.11 <6.12
- Affected versionversion=6.1.120 <6.2
- Affected versionversion=6.12.2 <6.13
- Affected versionversion=6.13
- Affected versionversion=6.6.64 <6.7
- Affected versionversion=6894717a1ea363c5a27010ba604f957c309d282d
- Affected versionversion=7b277bd569bb6a2777f0014f84b4344f444fd49d
- Affected versionversion=91e2a2e4d1336333804cd31162984f01ad8cc70f
- Affected versionversion=a9584c897d1cba6265c78010bbb45ca5722c88bc
- Affected versionversion=de5a44f351ca7efd9add9851b218f5353e2224b7
- Affected versionversion=fb91ce37dc9a37ea23cf32b6d7b667004e93d4c5
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Activity data is delayed. The latest report is Sep 28, 2026.
Weakness, pattern, technique
Public exploit references
- syzbot bnep_session reproducerproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Get started