Bluetooth: btusb: validate Realtek vendor event length
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: btusb: validate Realtek vendor event length
btusb_recv_event_realtek() reads the event code at data[0] and the Realtek subevent code at data[2] before deciding whether to consume a vendor event as a coredump.
For example, the two-byte event ff 00 contains a complete vendor-event header declaring zero parameters. The old classifier still reads a nonexistent third byte and can misclassify the event as a coredump if the adjacent byte is 0x34.
Require the HCI event header and first parameter to be present before inspecting the Realtek subevent code. Short events continue through the normal HCI receive path, which owns their protocol validation.
From the CVE record · Linux
The Linux kernel’s Bluetooth btusb Realtek event handler reads a subevent byte without first checking that it exists. A short vendor event can cause an out-of-bounds read and may be misclassified as a coredump if an adjacent byte is 0x34. The input does not specify attacker access or user-interaction requirements.
Engineers running Linux kernels with the Bluetooth btusb Realtek event handler should check their kernel version; affected versions are not specified.