In 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.
Update Linux/Linux to 0d4d6b083da9b033ddccef72d77f373c819ae3ea if you use the affected versions. Test the change in a non-production environment first.
Local check
hol-guard supply-chain scanBluetooth: hci_sync: Avoid use-after-free in dbg for hci_remove_adv_monitor() affects Linux/Linux (generic), Linux/Linux (generic). Severity is unknown. In 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.
AI coding agents often install or upgrade packages automatically in generic. A unknown vulnerability in a dependency can be pulled into a project through a normal install or update without a human reviewing the change, expanding the blast radius from a single package to every agent workspace that depends on it.
| Package | Affected range | Fixed version |
|---|
In 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.
Update Linux/Linux to 0d4d6b083da9b033ddccef72d77f373c819ae3ea if you use the affected versions. Test the change in a non-production environment first.
Local check
hol-guard supply-chain scanBluetooth: hci_sync: Avoid use-after-free in dbg for hci_remove_adv_monitor() affects Linux/Linux (generic), Linux/Linux (generic). Severity is unknown. In 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.
AI coding agents often install or upgrade packages automatically in generic. A unknown vulnerability in a dependency can be pulled into a project through a normal install or update without a human reviewing the change, expanding the blast radius from a single package to every agent workspace that depends on it.
| Package | Affected range | Fixed version |
|---|
| Linux/Linuxgeneric | >=7cf5c2978f23fdbb2dd7b4e8b07e362ae2d8211c <0d4d6b083da9b033ddccef72d77f373c819ae3ea || >=7cf5c2978f23fdbb2dd7b4e8b07e362ae2d8211c <bf00c2c8f6254f44ac041aa9a311ae9e0caf692b || >=7cf5c2978f23fdbb2dd7b4e8b07e362ae2d8211c <de6dfcefd107667ce2dbedf4d9337f5ed557a4a1 | 0d4d6b083da9b033ddccef72d77f373c819ae3ea, bf00c2c8f6254f44ac041aa9a311ae9e0caf692b, de6dfcefd107667ce2dbedf4d9337f5ed557a4a1 |
|---|
| Linux/Linuxgeneric | 6.0 | Not reported |
|---|
Fixed versions are reported by the source feed; confirm compatibility before updating.
Reported by CVE List V5 (cvelist).
HOL Guard can help your team review package activity against supported protection paths.
Explore HOL Guard| Linux/Linuxgeneric | >=7cf5c2978f23fdbb2dd7b4e8b07e362ae2d8211c <0d4d6b083da9b033ddccef72d77f373c819ae3ea || >=7cf5c2978f23fdbb2dd7b4e8b07e362ae2d8211c <bf00c2c8f6254f44ac041aa9a311ae9e0caf692b || >=7cf5c2978f23fdbb2dd7b4e8b07e362ae2d8211c <de6dfcefd107667ce2dbedf4d9337f5ed557a4a1 | 0d4d6b083da9b033ddccef72d77f373c819ae3ea, bf00c2c8f6254f44ac041aa9a311ae9e0caf692b, de6dfcefd107667ce2dbedf4d9337f5ed557a4a1 |
|---|
| Linux/Linuxgeneric | 6.0 | Not reported |
|---|
Fixed versions are reported by the source feed; confirm compatibility before updating.
Reported by CVE List V5 (cvelist).
HOL Guard can help your team review package activity against supported protection paths.
Explore HOL Guard