Bluetooth: hci_sync: Avoid use-after-free in dbg for hci_remove_adv_monitor()
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 6.1.42, 6.4.7
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: total
Summary
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.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- Linux Linux
From 7cf5c2978f23fdbb2dd7b4e8b07e362ae2d8211c · fixed in 0d4d6b083da9b033ddccef72d77f373c819ae3ea; From 7cf5c2978f23fdbb2dd7b4e8b07e362ae2d8211c · fixed in bf00c2c8f6254f44ac041aa9a311ae9e0caf692b; From 7cf5c2978f23fdbb2dd7b4e8b07e362ae2d8211c · fixed in de6dfcefd107667ce2dbedf4d9337f5ed557a4a1
- Linux Linux
6.0
- KernelLinux
From 6.0.0 · fixed in 6.1.42; From 6.2.0 · fixed in 6.4.7