Answer in brief
CVE-2023-54210 records a High severity (CVSS 7.8) vulnerability in Bluetooth: hci_sync: Avoid use-after-free in dbg for hci_remove_adv_monitor(). The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 7.8. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=7cf5c2978f23fdbb2dd7b4e8b07e362ae2d8211c <0d4d6b083da9b033ddccef72d77f373c819ae3ea || >=7cf5c2978f23fdbb2dd7b4e8b07e362ae2d8211c <bf00c2c8f6254f44ac041aa9a311ae9e0caf692b || >=7cf5c2978f23fdbb2dd7b4e8b07e362ae2d8211c <de6dfcefd107667ce2dbedf4d9337f5ed557a4a1 | 0d4d6b083da9b033ddccef72d77f373c819ae3ea, bf00c2c8f6254f44ac041aa9a311ae9e0caf692b, de6dfcefd107667ce2dbedf4d9337f5ed557a4a1 |
| Linux/Linuxgeneric | 6.0 | Not reported |
Published upstream
Dec 30, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Oct 28, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
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.
Quoted source text, attributed separately from HOL analysis.