Bluetooth: btmtk: validate WMT event SKB length before struct access
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
Bluetooth: btmtk: validate WMT event SKB length before struct access
btmtk_usb_hci_wmt_sync() casts the WMT event response SKB data to struct btmtk_hci_wmt_evt (7 bytes) and struct btmtk_hci_wmt_evt_funcc (9 bytes) without first checking that the SKB contains enough data. A short firmware response causes out-of-bounds reads from SKB tailroom.
Use skb_pull_data() to validate and advance past the base WMT event header. For the FUNC_CTRL case, pull the additional status field bytes before accessing them.
From the CVE record · Linux
The Linux kernel’s btmtk USB Bluetooth driver can read beyond the end of a WMT event response when firmware returns a response that is too short. The input does not establish how an attacker could cause this response or whether authentication, network access, or user interaction is required.
Engineers running Linux kernels with the btmtk USB Bluetooth driver should check whether their kernel includes the fix; affected versions were not provided.