CVE-2026-68393: Linux kernel · Bluetooth: hci_sync: extend conn_hash lookup critical sections
Affects Linux kernelSource CVE Database V5
Not known to be exploited · CVSS 8.8 High · fixed in d5efd6e4b8b0634af6843178fe1a7dd2b2178a3d : patch Linux kernel soon.
Data as of 26 Oct 2026, 16:53 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 15% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- CISA SSVC
- Exploitation
- No evidence of active exploitation and no public proof of concept
- Automatable
- Attackers cannot reliably automate steps 1–4 of the kill chain
- Technical impact
- Total control over the software or total information disclosure
CISA SSVC assessment, 2026-10-16.
- Patch
- Available – fixed in d5efd6e4b8b0634af6843178fe1a7dd2b2178a3d, 38326774df6198df0cc2744cc73bf77cb741c538, 83b7e67698d0b93f685875ce82c8d335436834f7 +3
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 10 Aug 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– |
Description
In the Linux kernel, the following vulnerability has been resolved: Bluetooth: hci_sync: extend conn_hash lookup critical sections Using RCU-protected pointers outside the critical sections without refcount is incorrect and may result to UAF. Extend critical section to cover both hci_conn_hash lookup and use of the returned conn. Add surrounding rcu_read_lock() also when return value is not used, in preparation for RCU lockdep requirement to hci_lookup_le_connect(). This avoids concurrent deletion of the conn before we are done dereferencing it. Also, make sure to hold hdev->lock when accessing hdev->accept_list.
References
- git.kernel.org/stable/c/3f98e7f38e1bb761a9964a8851f9c08e9c23b3dd (opens in a new tab)
- git.kernel.org/stable/c/83b7e67698d0b93f685875ce82c8d335436834f7 (opens in a new tab)
- git.kernel.org/stable/c/38326774df6198df0cc2744cc73bf77cb741c538 (opens in a new tab)
- git.kernel.org/stable/c/d5efd6e4b8b0634af6843178fe1a7dd2b2178a3d (opens in a new tab)