CVE-2025-44528: An issue in Texas Instruments LP-CC2652RB SimpleLink CC13XX CC26XX SDK 7.41.00.17 allows attackers to cause...
An issue in Texas Instruments LP-CC2652RB SimpleLink CC13XX CC26XX SDK 7.41.00.17 allows attackers to cause a Denial of Service (DoS) via sending a crafted LL_Pause_Enc_Req packet during the authentication and connection phase, causing a Denial of Service (DoS).
Security readout for executives and security teams
Plain-English summary
This CVE describes a denial-of-service flaw in Texas Instruments LP-CC2652RB SimpleLink CC13XX/CC26XX SDK 7.41.00.17. A malformed Bluetooth link-layer encryption pause request during connection setup can crash or disrupt availability. The sources do not identify data theft or integrity impact.
Executive priority
Treat this as a high-priority availability risk for TI-based BLE devices, especially operational or customer-facing deployments. Urgency depends on whether the affected SDK version is present and whether device downtime has business or safety impact.
Technical view
The record describes CWE-400 resource exhaustion triggered by a crafted LL_Pause_Enc_Req packet during authentication and connection. CVSS 3.1 is 7.5, with low complexity, no privileges, no user interaction, and high availability impact only. Affected CPE data is not populated.
Likely exposure
Exposure is most likely for products or firmware built with TI LP-CC2652RB SimpleLink CC13XX/CC26XX SDK 7.41.00.17 and using the affected BLE connection flow. The record does not list precise CPEs or downstream products.
Exploitation context
CISA KEV status is false in the supplied bundle. The CVE references a public GitHub PoC page, but the supplied sources do not provide evidence of active exploitation in the wild.
Researcher notes
The source data is narrow: one CVE description, CVSS vector, CWE-400, and a public PoC reference. It names the SDK version but lacks CPEs, vendor patch details, product matrix, and active-exploitation evidence.
Mitigation direction
Identify firmware using SimpleLink CC13XX/CC26XX SDK 7.41.00.17.
Check Texas Instruments guidance for fixed SDK or firmware updates.
Prioritize devices where availability loss affects operations or safety.
Restrict BLE pairing or connection exposure where operationally feasible.
Monitor device resets, disconnect spikes, and authentication failures.
Validation and detection
Inventory affected TI SDK versions in source and build artifacts.
Confirm whether deployed firmware implements the affected BLE connection path.
Review vendor advisories before declaring a device remediated.
Test fixes in a controlled lab without using production devices.
Correlate logs for abnormal connection-phase denial-of-service patterns.
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-400: 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.
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-400 · source CWE mapping
Uncontrolled Resource Consumption
Uncontrolled Resource Consumption represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.