LiveActive security incident?Get immediate response
CVE Record

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.

HighCVSS 7.8Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

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.
Prepared
Confidence
medium
Sources
8

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.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2023-53386 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
High
CVSS
7.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

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.

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.

ScoreVersionSeverityVectorExploitImpactSource
7.8CVSS 3.1HighCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H1.85.9CISA-ADP

Vulnerability scoring details

Base CVSS 3.1 score

7.8High
CVSS 3.1 vector shape for CVE-2023-53386Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

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.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
cvssV3_1other:ssvc
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxd7d41682efc25d58b5bd8b80e85e3c9ce586635c, d7d41682efc25d58b5bd8b80e85e3c9ce586635c, d7d41682efc25d58b5bd8b80e85e3c9ce586635c, d7d41682efc25d58b5bd8b80e85e3c9ce586635c, d7d41682efc25d58b5bd8b80e85e3c9ce586635c, d7d41682efc25d58b5bd8b80e85e3c9ce586635cunaffected
LinuxLinux5.7, 0, 5.10.195, 5.15.132, 6.1.53, 6.4.16, 6.5.3, 6.6affected
Weakness

CWE details

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.