CVE-2023-53386: Bluetooth: Fix potential use-after-free when clear keys
In the Linux kernel, the following vulnerability has been resolved:
Bluetooth: Fix potential use-after-free when clear keys
Similar to commit c5d2b6fa26b5 ("Bluetooth: Fix use-after-free in
hci_remove_ltk/hci_remove_irk"). We can not access k after kfree_rcu()
call.
Security readout for executives and security teams
Plain-English summary
CVE-2023-53386 is a Linux kernel Bluetooth bug where memory can be used after it is freed while clearing keys. A successful local attack could affect confidentiality, integrity, and availability. The source rates it high, but evidence provided does not show active exploitation.
Executive priority
Treat this as a high-priority kernel maintenance item for Linux fleets with Bluetooth exposure or local multi-user access. It is not currently evidenced as internet-exploited, but kernel memory-safety impact justifies timely patch planning.
Technical view
The issue is a CWE-416 use-after-free in Linux Bluetooth key-clearing logic. The fix notes that code must not access k after kfree_rcu(). CVSS 3.1 is 7.8 with local attack vector, low complexity, low privileges, no user interaction, and high impact to confidentiality, integrity, and availability.
Likely exposure
Exposure is most relevant to Linux systems running affected kernel versions with Bluetooth functionality present or enabled, especially endpoints, laptops, embedded devices, and multi-user Linux hosts. The source bundle identifies Linux kernel versions and upstream stable commits, but not distribution package names.
Exploitation context
The CVSS vector indicates exploitation requires local access and low privileges, with no user interaction. CISA KEV status is false in the source bundle, and no cited source in the bundle confirms exploitation in the wild.
Researcher notes
Analysis should focus on the Bluetooth key-clearing path and the post-kfree_rcu() access described by the fix. The bundle provides upstream stable commit references but limited product-range detail; validate exact exposure against distro backports and kernel configuration.
Mitigation direction
Apply vendor Linux kernel updates that include the referenced upstream stable fixes.
Check distribution advisories for exact fixed kernel package versions.
Prioritize Linux systems with Bluetooth enabled and local user access.
Track the CVE record for updated affected-version guidance.
Do not rely on upstream commit IDs alone for distro package status.
Validation and detection
Inventory Linux kernel versions across managed systems.
Identify systems with Bluetooth hardware, services, or modules enabled.
Map installed distro kernel packages to vendor fixed-version advisories.
Confirm deployed kernels include the relevant stable fix commits.
Retest after reboot to verify the fixed kernel is running.
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.
cwe · low confidence lookup
CWE-416: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
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.
1CVSS vectors
3Timeline events
1ADP providers
7Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-416 · source CWE mapping
Use After Free
Use After Free represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.