Bluetooth: hci_sync: Avoid use-after-free in dbg for hci_remove_adv_monitor()
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
6.1.426.4.76.5In the Linux kernel, the following vulnerability has been resolved:
Bluetooth: hci_sync: Avoid use-after-free in dbg for hci_remove_adv_monitor()
KASAN reports that there's a use-after-free in hci_remove_adv_monitor(). Trawling through the disassembly, you can see that the complaint is from the access in bt_dev_dbg() under the HCI_ADV_MONITOR_EXT_MSFT case. The problem case happens because msft_remove_monitor() can end up freeing the monitor structure. Specifically: hci_remove_adv_monitor() -> msft_remove_monitor() -> msft_remove_monitor_sync() -> msft_le_cancel_monitor_advertisement_cb() -> hci_free_adv_monitor()
Let's fix the problem by just stashing the relevant data when it's still valid.
From the CVE record · Linux
The Linux kernel's Bluetooth hci_remove_adv_monitor() can access a monitor structure after it has been freed during monitor removal. The input does not specify how an attacker could trigger this, or whether network access, authentication, or user interaction is required.
Engineers running the Linux kernel should check whether their version includes the Bluetooth hci_sync fix; affected versions are not specified.