CVE-2023-54210
- Source
- https://cve.org/CVERecord?id=CVE-2023-54210
- Import Source
- https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2023-54210.json
- JSON Data
- https://api.osv.dev/v1/vulns/CVE-2023-54210
- Downstream
- Related
- Published
- 2025-12-30T12:11:08Z
- Modified
- 2026-08-12T03:51:30Z
- Severity
-
- 7.8 (High) CVSS_V3 - CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H CVSS Calculator
- Summary
- Bluetooth: hci_sync: Avoid use-after-free in dbg for hci_remove_adv_monitor()
- Details
-
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.
- Database specific
{ "cna_assigner": "Linux", "osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2023/54xxx/CVE-2023-54210.json" }- References
-
- https://git.kernel.org/stable/c/0d4d6b083da9b033ddccef72d77f373c819ae3ea
- https://git.kernel.org/stable/c/bf00c2c8f6254f44ac041aa9a311ae9e0caf692b
- https://git.kernel.org/stable/c/de6dfcefd107667ce2dbedf4d9337f5ed557a4a1
- https://github.com/CVEProject/cvelistV5/tree/main/cves/2023/54xxx/CVE-2023-54210.json
- https://nvd.nist.gov/vuln/detail/CVE-2023-54210
- https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git