Bluetooth: btusb: reorder cleanup in btusb_disconnect to avoid UAF
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ fd913ef7ce619467c6b0644af48ba1fec499c623 · < 95b9b98c93b1c0916a3d4cf4540b7f5d69145a0d| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
Bluetooth: btusb: reorder cleanup in btusb_disconnect to avoid UAF
There is a KASAN: slab-use-after-free read in btusb_disconnect(). Calling "usb_driver_release_interface(&btusb_driver, data->intf)" will free the btusb data associated with the interface. The same data is then used later in the function, hence the UAF.
Fix by moving the accesses to btusb data to before the data is free'd.
From the CVE record · Linux
The Linux kernel’s btusb_disconnect() reads btusb data after releasing the interface that frees it. This can cause a use-after-free read during Bluetooth USB device disconnection; the input does not specify how an attacker could trigger it or whether authentication or user interaction is required.
Anyone running the Linux kernel should check whether their version includes the btusb_disconnect() fix; affected versions are not specified.