Bluetooth: hci_event: validate skb length for unknown CC opcode
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
Bluetooth: hci_event: validate skb length for unknown CC opcode
In hci_cmd_complete_evt(), if the command complete event has an unknown opcode, we assume the first byte of the remaining skb->data contains the return status. However, parameter data has previously been pulled in hci_event_func(), which may leave the skb empty. If so, using skb->data[0] for the return status uses un-init memory.
The fix is to check skb->len before using skb->data.
From the CVE record · Linux
The Linux kernel's Bluetooth command-complete handler can read uninitialized memory when it processes an event with an unknown opcode and no remaining parameter data. The input does not establish how an attacker could trigger this condition or whether authentication or user interaction is required.
Anyone running the Linux kernel should check whether their build includes the Bluetooth hci_event fix; affected versions were not specified.