CVE-2026-31497: Bluetooth: btusb: clamp SCO altsetting table indices

Published Apr 22, 2026
·
Updated

Bluetooth: btusb: clamp SCO altsetting table indices

Affected Software

18 affected componentsFixes available
Linux btusb (Linux kernel)
Linux Linux kernel>=5.8.1<5.10.253
Linux Linux kernel>=5.11<5.15.203
Linux Linux kernel>=5.16<6.1.168
Linux Linux kernel>=6.2<6.6.131
Linux Linux kernel>=6.7<6.12.80
Linux Linux kernel>=6.13<6.18.21
Linux Linux kernel>=6.19<6.19.11
Linux Linux kernel=5.8
Linux Linux kernel=7.0-rc1
Linux Linux kernel=7.0-rc2
Linux Linux kernel=7.0-rc3
Linux Linux kernel=7.0-rc4
Linux Linux kernel=7.0-rc5
Linux Linux kernel=7.0-rc6
Linux Linux kernel=7.0-rc7
Microsoft azl3 kernel 6.6.130.1-3
debian/linux
6.1.176-16.1.190-16.12.107-16.12.115-27.2.12-17.2.15-1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade debian/linux to a version that resolves this vulnerability.

    Fixed in 6.1.176-1Fixed in 6.1.190-1Fixed in 6.12.107-1Fixed in 6.12.113-1Fixed in 7.2.12-1Fixed in 7.2.13-1
  2. Compensating control

    In btusb_work(), clamp the SCO alternate-setting table index to the last available entry before indexing alts[], so values of data->sco_num beyond the three-entry table select the highest supported alternate setting without reading past alts[].

Event History

Apr 22, 2026
CVE Published
via MITRE·01:54 PM
Data Sourced
via MITRE·01:54 PM
Description
Data Sourced
via NVD·02:16 PM
RemedyDescriptionSeverityAffected Software
Apr 23, 2026
Data Sourced
via Microsoft·08:05 AM
DescriptionSeverityWeaknessAffected Software

Parent advisories

This vulnerability appears in the following advisories.

Peer vulnerabilities

Found alongside the following vulnerabilities.

Frequently Asked Questions

1

What access does an attacker need to trigger this issue?

The CVSS vector indicates local access and low privileges are required. No user interaction is required.

2

Which systems are exposed?

Systems using the Linux kernel btusb driver are affected when handling SCO traffic with transparent voice settings. The issue involves more than three active SCO links causing the driver to index beyond its three-entry alternate-setting table.

3

What is the impact if exploitation succeeds?

The stated impact is availability only, with no confidentiality or integrity impact listed. The vulnerability can result in a denial of service.

4

What should be done if patching cannot happen immediately?

The provided data identifies a patch as available. No alternative mitigation or configuration workaround is provided.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203