CVE-2026-98737: Linux kernel · Bluetooth: hci_sync: Fix inquiry cache use-after-free
Source GCVE Database
Not known to be exploited · fixed in ddc9edb244cc8b5266595e8fc220e7813f2b603a : update Linux kernel when convenient.
Data as of 26 Oct 2026, 13:47 UTC
Rated by Threat Radar · CVSS not yet scored by NVD
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 9% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in ddc9edb244cc8b5266595e8fc220e7813f2b603a, a642f498f0b08f2aa9f4a69468db92f57a72349d, 333257e6e4a7bcaaea82fd357121d0f1e6b76c7b +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 has been implemented in the Linux kernel to address this issue by correcting locking behavior and memory handling in the Bluetooth inquiry cache code. Users should apply the official kernel updates containing this fix when available. Patch status is not explicitly confirmed in the provided data; check the vendor advisory for current remediation guidance.
Description
A use-after-free vulnerability in the Linux kernel's Bluetooth hci_sync component was resolved. The issue arises from improper locking during inquiry cache lookups and updates, leading to potential access of freed memory. The fix involves holding the appropriate lock across lookups and copying remote addresses before unlocking to prevent stale pointer usage.
References
- nvd.nist.gov/vuln/detail/CVE-2026-98737 (opens in a new tab)
- git.kernel.org/stable/c/333257e6e4a7bcaaea82fd357121d0f1e6b76c7b (opens in a new tab)
- git.kernel.org/stable/c/52edf1c0e59dea37b8368c4a2559dca96b2fdfea (opens in a new tab)
- git.kernel.org/stable/c/8ed67535fdff40ca652bcd4ac7da68d11d01bd34 (opens in a new tab)
- git.kernel.org/stable/c/a642f498f0b08f2aa9f4a69468db92f57a72349d (opens in a new tab)