Security readout for executives and security teams
Plain-English summary
This vulnerability can let a nearby Bluetooth attacker crash or disrupt devices built with the named Texas Instruments SimpleLink BLE SDK version. The known impact is denial of service, not data theft or code execution. Business urgency depends on whether products use this SDK and whether BLE availability matters operationally.
Executive priority
Treat as a targeted availability risk. It is not currently supported as actively exploited, but organizations shipping or operating affected BLE devices should confirm exposure and track vendor remediation.
Technical view
CVE-2025-44525 describes insufficient permission checks on critical fields in BLE data packets in Texas Instruments CC2652RB LaunchPad SimpleLink CC13XX/CC26XX SDK 7.41.00.17. A crafted BLE length request can cause denial of service. CVSS 3.1 is 6.5 with adjacent attack vector and high availability impact.
Likely exposure
Likely exposure is limited to devices or firmware built with the named TI SimpleLink CC13XX/CC26XX SDK 7.41.00.17 and using affected BLE functionality. The structured CVE affected-product fields are listed as n/a, so asset confirmation is required.
Exploitation context
The CVE is not listed as KEV in the provided bundle. A public GitHub PoC-style reference is cited, but the provided evidence does not establish active exploitation in the wild. Attack prerequisites appear local or adjacent BLE radio proximity based on the CVSS vector.
Researcher notes
The CVE data is sparse: affected CPE fields are empty, and only the description names TI hardware and SDK context. Avoid broad product assumptions. Focus analysis on SDK lineage, BLE stack behavior, and vendor confirmation of corrected permission checks.
Mitigation direction
- Inventory firmware built with SimpleLink CC13XX/CC26XX SDK 7.41.00.17.
- Check Texas Instruments guidance for fixed SDK versions or vendor mitigations.
- Prioritize updates for devices where BLE availability is operationally important.
- Reduce unnecessary BLE exposure where configuration allows.
- Monitor affected devices for unexpected resets or availability loss.
Validation and detection
- Confirm whether products use TI CC2652RB or related CC13XX/CC26XX BLE firmware.
- Verify the exact SimpleLink SDK version used in production builds.
- Review vendor advisories before performing any lab validation.
- Assess whether BLE connectivity is exposed in deployed operating environments.
- Map affected assets to business processes requiring continuous availability.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-284: Authorization and privilege behavior lookup
Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. 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 lookupCVE-2025-44525 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 6.5 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
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.
SSVC decision data
CVSS vector scores
1 official scoreWe 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.
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H2.83.6CISA-ADPVulnerability scoring details
Base CVSS 3.1 score
6.5MediumVector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/yangting111/BLE_TEST/blob/main/result/PoC/TI/Length_Req_MaxRxBytes.mdCVE reference, mitre
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Access Control
Improper Access Control represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.