CVE-2026-31497: Linux kernel · Bluetooth: btusb: clamp SCO altsetting table indices
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in 1019028eb124564cf7bca58a16f1df8a1ca30726 : update Linux kernel when convenient.
Data as of 5 Nov 2026, 22:19 UTC
Rated Medium by Threat Radar's AI analysis · No CVSS score from NVD or the CNA
Thin evidence
One scorer or none- 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
- Limited control over the software or limited information exposure
CISA SSVC assessment, 2026-11-05.
- Patch
- Available – fixed in 1019028eb124564cf7bca58a16f1df8a1ca30726, 834cf890d2c3d29cbfa1ee2376c40469c28ec297, 476c9262b430c38c6a701a3b8176a3f48689085b +5
Exploitation evidence
Disclosed: evidence found.
CVE published 22 Apr 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: 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 5 Nov 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 is available and has been applied in the Linux kernel. Users should update to a fixed kernel version containing the patches identified by the provided commit hashes to mitigate this issue.
Description
A vulnerability in the Linux kernel Bluetooth driver (btusb) was fixed by clamping SCO altsetting table indices. The issue involved indexing a three-entry lookup table for USB alternate settings without properly constraining the index, potentially causing out-of-bounds access. The fix caps the index to the highest supported alternate setting to prevent reading past the table.
References
- git.kernel.org/stable/c/312c4450fe23014665c163f480edd5ad2e27bbb8 (opens in a new tab)
- git.kernel.org/stable/c/9dd13a8641de79bc1bc93da55cdd35259a002683 (opens in a new tab)
- git.kernel.org/stable/c/476c9262b430c38c6a701a3b8176a3f48689085b (opens in a new tab)
- git.kernel.org/stable/c/6fba3c3d48c927e55611a0f5ea34da88138ed0ff (opens in a new tab)
- git.kernel.org/stable/c/834cf890d2c3d29cbfa1ee2376c40469c28ec297 (opens in a new tab)
- git.kernel.org/stable/c/1019028eb124564cf7bca58a16f1df8a1ca30726 (opens in a new tab)
- git.kernel.org/stable/c/21c254202f9d78abe0fcd642a92966deb92bd226 (opens in a new tab)
- git.kernel.org/stable/c/129fa608b6ad08b8ab7178eeb2ec272c993aaccc (opens in a new tab)