CVE-2026-98734: Linux kernel · Bluetooth: hci_core: Serialize SCO and ISO scheduling with teardown
Source GCVE Database
Not known to be exploited · fixed in f997e03e2ef58aa7114828c9d924e515a9a1db9c : patch Linux kernel soon.
Data as of 26 Oct 2026, 17:16 UTC
Rated by Threat Radar · CVSS not yet scored by NVD
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 5% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in f997e03e2ef58aa7114828c9d924e515a9a1db9c, ecdb1c66d8e14e63731c52d6fbcfa604064913c4, 101825c09ad6b7daa6cf4c9e6b1720b13de15596 +2
Exploitation evidence
Disclosed: evidence found.
CVE published 18 Oct 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
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in– |
AI-suggested
A fix for this vulnerability has been implemented in the Linux kernel by serializing SCO and ISO scheduling with connection teardown using the hci_dev_lock() mutex. Users should update to the fixed Linux kernel version once available.
Description
A use-after-free vulnerability in the Linux kernel's Bluetooth hci_core component was resolved. The flaw involved improper serialization of SCO and ISO scheduling with connection teardown, leading to potential access of freed memory. The issue was fixed by holding a device lock across connection selection and transmission, preventing concurrent access after connection removal.
References
- nvd.nist.gov/vuln/detail/CVE-2026-98734 (opens in a new tab)
- git.kernel.org/stable/c/101825c09ad6b7daa6cf4c9e6b1720b13de15596 (opens in a new tab)
- git.kernel.org/stable/c/1681f97afdf92e8557f2f3118ddc898471b5d299 (opens in a new tab)
- git.kernel.org/stable/c/848a7a91c7f03675d3bd8db6f7721cbf9cb50e21 (opens in a new tab)
- git.kernel.org/stable/c/ecdb1c66d8e14e63731c52d6fbcfa604064913c4 (opens in a new tab)
- git.kernel.org/stable/c/f997e03e2ef58aa7114828c9d924e515a9a1db9c (opens in a new tab)