LiveActive security incident?Get immediate response
CVE Record

CVE-2023-54210: Bluetooth: hci_sync: Avoid use-after-free in dbg for hci_remove_adv_monitor()

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.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

This is a Linux kernel Bluetooth bug where debug logging can read a monitor object after it has already been freed. The public bundle does not provide CVSS, CWE, attack vector, or confirmed exploitation. Business urgency depends on whether affected Linux kernels with Bluetooth functionality are deployed in exposed or sensitive environments.

Executive priority

Track as a kernel memory-safety patching item. Escalate above routine maintenance only where Bluetooth is enabled on sensitive systems or vendor guidance raises severity.

Technical view

CVE-2023-54210 is a use-after-free in hci_remove_adv_monitor() under the HCI_ADV_MONITOR_EXT_MSFT path. KASAN identified access from bt_dev_dbg() after msft_remove_monitor() can free the monitor through the documented callback chain. The fix stores needed data while the structure remains valid.

Likely exposure

Potential exposure is limited to Linux systems running affected kernel versions or commit ranges with relevant Bluetooth advertising monitor functionality. The bundle lists Linux 6.0, 6.1.42, 6.4.7, and 6.5 as affected, but does not describe distribution-specific packages.

Exploitation context

No active exploitation is stated. KEV is false, and the provided sources do not describe exploitability, required privileges, proximity, or user interaction. Treat this as a kernel memory-safety issue requiring vendor correlation, not as confirmed weaponized activity.

Researcher notes

Evidence is limited to the CVE record and Linux stable commits. The root cause is a stale monitor pointer used for debug output after msft_remove_monitor() may free it. No exploit primitive, trigger conditions, or downstream distribution impact is provided.

Mitigation direction

  • Check kernel vendor advisories for CVE-2023-54210 package status.
  • Update to a kernel containing the referenced stable fixes.
  • Prioritize systems using Bluetooth in sensitive or fleet-managed environments.
  • Disable unnecessary Bluetooth functionality where operationally acceptable until patched.

Validation and detection

  • Inventory Linux kernel versions across servers, workstations, and embedded devices.
  • Map installed kernels to vendor advisories for CVE-2023-54210.
  • Confirm whether Bluetooth support and advertising monitor code paths are enabled.
  • Verify patched systems include one of the referenced stable commits or vendor equivalent.
Prepared
Confidence
medium
Sources
5

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2023-54210 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
0ADP providers
4Source links

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux7cf5c2978f23fdbb2dd7b4e8b07e362ae2d8211c, 7cf5c2978f23fdbb2dd7b4e8b07e362ae2d8211c, 7cf5c2978f23fdbb2dd7b4e8b07e362ae2d8211cunaffected
LinuxLinux6.0, 0, 6.1.42, 6.4.7, 6.5affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.