CVE-2026-98109: Linux kernel · Bluetooth: hci_core: Fix race condition during device registration
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in d427b1c71d9798083e954d3c13469dc0a2305868 : update Linux kernel when convenient.
Data as of 26 Oct 2026, 16:39 UTC
Rated Medium by Threat Radar's AI analysis · CVSS not yet scored by NVD
- EPSS
- 0.08% chance of exploitation in 30 days – higher than 0% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in d427b1c71d9798083e954d3c13469dc0a2305868, b1faf348c29e6f8302ec7769cbf1c1ef05be014f, a11ebe8dc0333fb870bbbb656b34690e87ee3f98 +4
Exploitation evidence
Disclosed: evidence found.
CVE published 25 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in– |
AI-suggested
A fix is available and has been applied in Linux kernel versions 6.5 and 6.6 as well as specific commits identified in the established facts. Users and administrators should upgrade to Linux kernel version 6.5 or later to ensure this race condition is resolved. No additional mitigation actions are required beyond applying the official fix.
Description
A race condition vulnerability in the Linux kernel Bluetooth hci_core subsystem during device registration could lead to a DEBUG_LOCKS warning due to an uninitialized mutex being accessed. The issue occurs when asynchronous work items run before device structures and extensions are fully initialized. This has been fixed by reordering initialization steps to ensure proper setup before concurrent access.
References
- git.kernel.org/stable/c/593e64f64a20b25e4042c3ee863119eb7f991785 (opens in a new tab)
- git.kernel.org/stable/c/b1faf348c29e6f8302ec7769cbf1c1ef05be014f (opens in a new tab)
- git.kernel.org/stable/c/a11ebe8dc0333fb870bbbb656b34690e87ee3f98 (opens in a new tab)
- git.kernel.org/stable/c/d427b1c71d9798083e954d3c13469dc0a2305868 (opens in a new tab)
- git.kernel.org/stable/c/57938bbdb9bf7fd41cbd5cd509ec10c4b22bec18 (opens in a new tab)