LiveActive security incident?Get immediate response
CVE Record

CVE-2021-34149: The Bluetooth Classic implementation on the Texas Instruments CC256XCQFN-EM does not properly handle the re...

The Bluetooth Classic implementation on the Texas Instruments CC256XCQFN-EM does not properly handle the reception of continuous LMP_AU_Rand packets, allowing attackers in radio range to trigger a denial of service (deadlock) of the device by flooding it with LMP_AU_Rand packets after the paging procedure.

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

Security readout for executives and security teams

Plain-English summary

This vulnerability lets a nearby attacker crash or deadlock some Texas Instruments Bluetooth Classic implementations by abusing Bluetooth link-management traffic. It is a denial-of-service issue, not evidence of data theft or remote internet compromise. The source bundle does not provide CVSS, CWE, fixed versions, or proof of active exploitation.

Executive priority

Treat this as a targeted availability risk for Bluetooth-enabled products, especially embedded or operational devices. Prioritize asset identification and vendor guidance review over emergency response unless critical devices are affected.

Technical view

CVE-2021-34149 concerns improper handling of continuous LMP_AU_Rand packets in the Bluetooth Classic implementation on TI CC256XCQFN-EM. After paging, repeated packets can cause a device deadlock. The issue requires Bluetooth radio range and targets availability. Public references include TI CC256x materials and the BrakTooth paper.

Likely exposure

Exposure is likely limited to products embedding the referenced TI CC256x Bluetooth Classic hardware/software stack and reachable within Bluetooth radio range. Internet-facing exposure is not indicated by the sources.

Exploitation context

The CVE describes a radio-range denial-of-service condition after Bluetooth paging. The bundle marks KEV as false and provides no cited evidence of active exploitation in the wild.

Researcher notes

The source bundle lacks CVSS, CWE, exact affected version ranges, and named fixed releases. Validate product impact through TI documentation and the cited BrakTooth research. Avoid assuming all CC256x deployments are vulnerable without component and software-stack confirmation.

Mitigation direction

  • Identify products using TI CC256x or CC256XCQFN-EM Bluetooth Classic components.
  • Check Texas Instruments guidance for affected software packages and supported updates.
  • Apply vendor-supported firmware or software updates where available.
  • Limit unnecessary Bluetooth discoverability or pairing exposure in sensitive environments.
  • Plan operational recovery for devices where updates are unavailable.

Validation and detection

  • Inventory deployed Bluetooth devices and map their TI chipset or module versions.
  • Compare device firmware and stack versions against TI product and software-package guidance.
  • Confirm whether Bluetooth Classic is enabled on exposed or safety-critical devices.
  • Review logs or monitoring for unexplained Bluetooth device deadlocks or resets.
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-2021-34149 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
0Timeline events
0ADP providers
4Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

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