Bluetooth: btusb: clamp SCO altsetting table indices
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ baac6276c0a9f36f1fe1f00590ef00d2ba5ba626 · < 1019028eb124564cf7bca58a16f1df8a1ca30726| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
Bluetooth: btusb: clamp SCO altsetting table indices
btusb_work() maps the number of active SCO links to USB alternate settings through a three-entry lookup table when CVSD traffic uses transparent voice settings. The lookup currently indexes alts[] with data->sco_num - 1 without first constraining sco_num to the number of available table entries.
While the table only defines alternate settings for up to three SCO links, data->sco_num comes from hci_conn_num() and is used directly. Cap the lookup to the last table entry before indexing it so the driver keeps selecting the highest supported alternate setting without reading past alts[].
From the CVE record · Linux
The Linux kernel Bluetooth btusb driver can read past a three-entry USB alternate-setting table when more than three SCO links are active under transparent voice settings. The input does not specify how an attacker could trigger this condition or whether network access, authentication, or user interaction is required.
Engineers running Linux kernels with the Bluetooth btusb driver should check their systems; affected versions are not specified.