CVE-2026-98111: Linux kernel · Bluetooth: btintel: validate version TLV value lengths
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in e9cf7f175c00d36b060828f4eac8d2e246ee079b : update Linux kernel when convenient.
Data as of 26 Oct 2026, 12:55 UTC
Rated Medium by Threat Radar's AI analysis · CVSS not yet scored by NVD
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 6% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in e9cf7f175c00d36b060828f4eac8d2e246ee079b, a086c0892969bf8a0151b0f12bd14a68827c88b2, 83499ac3ca62e43ed40f7574b13ed398a6891511 +2
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
|
| 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 and is available in the Linux kernel source code commits referenced. Users and administrators should update their Linux kernel to a fixed version beyond 5.10 where this issue is resolved. No additional mitigation steps are indicated.
Description
A vulnerability in the Linux kernel Bluetooth subsystem (btintel) was identified where the function parsing version TLV values did not properly validate the length of the value for specific TLV types. This flaw could lead to out-of-bounds reads when processing malformed Bluetooth responses. The issue has been fixed by rejecting TLV values shorter than the minimum required length and responses missing the Command Complete Status field.
References
- git.kernel.org/stable/c/e9cf7f175c00d36b060828f4eac8d2e246ee079b (opens in a new tab)
- git.kernel.org/stable/c/83499ac3ca62e43ed40f7574b13ed398a6891511 (opens in a new tab)
- git.kernel.org/stable/c/76948d207d0978a613ce06a05cba07284a5578a7 (opens in a new tab)
- git.kernel.org/stable/c/5ec43df2830b73e004147303bf7914ca884d6770 (opens in a new tab)
- git.kernel.org/stable/c/a086c0892969bf8a0151b0f12bd14a68827c88b2 (opens in a new tab)