Security Advisory

CVE-2025-10457: Zephyr BLE Unexpected L2CAP Response

Last updated:
  • CVE-2025-10457

CVE-2025-10457 is a Bluetooth L2CAP flaw in the Zephyr RTOS: the function that handles LE connection responses does not check whether the device ever sent a connection request and relies only on a matching identifier, so a peer can inject responses and confuse the protocol state. NVD scores it 8.1 for Zephyr through 4.1.0.

Vulnerability summary

CVSS base score

8.1

High severity

EPSS score (FIRST)

0.4%

Probability of exploitation in the wild in the next 30 days

CISA KEV catalog

No

Not listed

Published

Vulnerability ID: CVE-2025-10457 · Source: NVD

Affected components

ComponentCPEVersion range
Zephyr RTOS Bluetooth host L2CAP (le_conn_rsp)cpe:2.3:o:zephyrproject:zephyr:*:*:*:*:*:*:*:*through 4.1.0 (NVD); fixed by PR 94080, merged 2025-08-08, first tagged in v4.3.0 (2025-11-13)

What does this mean for affected devices?

Zephyr published CVE-2025-10457 as GHSA-xqj6-vh76-2vv8 on 2025-09-19. The advisory says le_conn_rsp "fails to verify whether a connection response is actually expected—i.e., whether the device initiated a connection request. Instead, it only checks if the identifier matches". It adds that this leads to state confusion "when coupled with" CVE-2025-10456, where an overflowing credit indication makes the device send a request and allocate an identifier an attacker can then answer. Zephyr lists the impact as "protocol state confusion, potentially resulting in security issues, memory corruption, or denial of service".

The two scores differ widely. NVD scores it 8.1, vector CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H. Zephyr, as the CNA, scores it 4.3 (A:L only) and assigns CWE-358 (Improperly Implemented Security Check for Standard). NVD lists Zephyr through 4.1.0 (NVD). The site uses the NVD Primary score.

The fix is PR 94080, "Add req/rsp l2cap validation". The Zephyr 2025 vulnerability list says it "has been fixed in main for v4.2.0", but the PR was merged on 2025-08-08, after v4.2.0 was tagged on 2025-07-19. GitHub's tag comparison shows the commit is first contained in v4.3.0, released 2025-11-13, and the list names no backport to the 3.7 LTS branch or to 4.2.x. A device on Zephyr 4.2.x therefore still has this bug.

Zephyr provides the BLE host stack on many peripherals, and the SweynTooth disclosure tested "Nordic Semiconductor (Zephyr Project Stack) nRF51/52" parts, so the flaw ships inside device firmware wherever Bluetooth is enabled. The code is in the L2CAP signalling path every LE connection uses, which makes it reachable from any device in radio range that can connect.

The CVE is not in the CISA KEV catalog as of 2026-11-16 (catalog version 2026.11.13). FIRST EPSS gives it 0.00396, the 34.4th percentile, in the 2026-11-15 dataset (CISA KEV, FIRST EPSS).

Move Bluetooth-enabled Zephyr products to v4.3.0 or later, or cherry-pick PR 94080 together with the CVE-2025-10456 fix, and rebuild. Our Bluetooth LE security guide explains why BLE stacks need version tracking, and our firmware SBOM guide shows how to record the RTOS version. CVE-2025-7403 is another Zephyr Bluetooth flaw from the same disclosure.

How to fix this class of issueNo dedicated SoftWSP guide covers this weakness class; the fix is usually the vendor patch or firmware update referenced above. Our related guide explains how to plan and verify it: NIST SP 800-40 Rev. 4: enterprise patch management planning, explained.

Evidence

  • le_conn_rsp does not verify a response is expected, only identifier match; state confusion when combined with GHSA-hcc8-3qr7-c9m8; impact: state confusion, memory corruption or DoS; published 2025-09-19; CNA 4.3, CWE-358. — Zephyr GHSA-xqj6-vh76-2vv8
  • NVD CVSS 3.1 8.1 (AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H); CNA 4.3 (A:L); Zephyr through 4.1.0. — NVD
  • Listed as fixed in main for v4.2.0 by PR 94080; no other branch listed. — Zephyr Project 2025 vulnerabilities
  • PR 94080 merged 2025-08-08; GitHub compare: not in v4.2.0 (2025-07-19), contained in v4.3.0 (2025-11-13). — Zephyr PR 94080
  • SweynTooth tested Nordic nRF51/52 with the Zephyr Project stack. — SweynTooth disclosure
  • Not in the CISA KEV catalog as of 2026-11-16 (catalog version 2026.11.13). — CISA KEV
  • EPSS 0.00396 (34.4th percentile), dataset 2026-11-15, read 2026-11-16. — FIRST EPSS

Related advisories

Sources

  1. NVD
  2. Zephyr security advisory GHSA-xqj6-vh76-2vv8
  3. Zephyr Project: 2025 security vulnerabilities
  4. Zephyr PR 94080: Bluetooth: Host: Add req/rsp l2cap validation
  5. CISA KEV
  6. FIRST EPSS

Frequently asked questions

Which Zephyr release fixes CVE-2025-10457?

v4.3.0, released 2025-11-13, is the first tag that contains the fix (PR 94080, merged 2025-08-08). The Zephyr list says v4.2.0, but that release was tagged on 2025-07-19, before the merge (per GitHub and the Zephyr vulnerability list).

Why is NVD's score (8.1) so much higher than Zephyr's (4.3)?

NVD rates high integrity and availability impact, while Zephyr's CNA vector rates only low availability impact. The advisory's own impact text mentions possible memory corruption as well as denial of service (per NVD and GHSA-xqj6-vh76-2vv8).

Should CVE-2025-10457 be patched together with CVE-2025-10456?

Yes. Zephyr's advisory says the unchecked response handling causes state confusion when combined with CVE-2025-10456, and both fixes first ship in v4.3.0 on the main line (per GHSA-xqj6-vh76-2vv8 and GitHub).

Is CVE-2025-10457 exploited?

It is not in the CISA KEV catalog as of 2026-11-16 (catalog version 2026.11.13). FIRST EPSS gives it 0.00396, the 34.4th percentile, in the 2026-11-15 dataset (per CISA KEV and FIRST EPSS).