Skip to content

Bluetooth: le_conn_rsp does not sanitize CID, MTU, MPS values

High
ceolin published GHSA-vmww-237q-2fwp Sep 19, 2025

Package

zephyr (zephyr)

Affected versions

<= 4.1

Patched versions

None

Description

Parameters are not validated or sanitized, and are later used in various internal operations.

  1. le_conn_rsp is the function responsible for handling connection response when the BLE device initiated a connection request himself.
  2. On the response the other device respond its own parameters of the connections:
    a. The channel ID it would like to receive data on (CID)
    b. The device MTU (Maximum Transmission Unit)
    c. The MPS (Maximum PDU size)
image
  1. These values are not sanitized at all, and are later in various logical and functional operations
  2. Because of Vulnerability GHSA-hcc8-3qr7-c9m8 and Vulnerability GHSA-xqj6-vh76-2vv8 we would be able to take advantage of it regardless of whether the device initiates a connection or not!
  3. Even without those primitives, any request made by the device will make it vulnerable!
  4. This issue leads to a severe buffer overflow (caused by integer underflow) in the ATT module. For Example (Other examples may exist):
    a. The ATT module assumes a minimum bt_att_mtu return value. However, as the value is small an underflow will occur leading to more data pushed.
image

Patches

For more information

If you have any questions or comments about this advisory:

embargo: 2025-09-05

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Adjacent
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
High

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:H

CVE ID

CVE-2025-10458

Weaknesses

Improper Handling of Length Parameter Inconsistency

The product parses a formatted message or structure, but it does not handle or incorrectly handles a length field that is inconsistent with the actual length of the associated data. Learn more on MITRE.