CVE-2025-10456 is a Bluetooth L2CAP flaw in the Zephyr RTOS: a crafted credit indication that overflows a channel's credits makes the device send a disconnection request for any channel ID, including fixed channels such as SMP and ATT, which leads to assertion failures, crashes or memory corruption. NVD scores it 6.5 for Zephyr through 4.1.0.
Vulnerability summary
CVSS base score
6.5
Medium severity
EPSS score (FIRST)
0.2%
Probability of exploitation in the wild in the next 30 days
CISA KEV catalog
No
Not listed
Published
Vulnerability ID: CVE-2025-10456 · Source: NVD
Affected components
| Component | CPE | Version range |
|---|---|---|
| Zephyr RTOS Bluetooth host L2CAP (le_credits, subsys/bluetooth/host/l2cap.c) | cpe:2.3:o:zephyrproject:zephyr:*:*:*:*:*:*:*:* | through 4.1.0 (NVD); fixed by PR 93576 (merged 2025-08-01, first tagged in v4.3.0) and the v3.7 backport PR 100474 (in v3.7.2) |
What does this mean for affected devices?
Zephyr published CVE-2025-10456 as GHSA-hcc8-3qr7-c9m8 on 2025-09-19. The advisory traces the bug to le_credits in subsys/bluetooth/host/l2cap.c, which parses the L2CAP Flow Control Credit Indication. Two requests, for example one adding 22 credits and one adding 65535, correctly trigger the overflow check, and the code sends a disconnection request. That request allocates an identifier, which makes the device accept a matching response later, and the code "does not check that the CID is 0x05 (LE SIGNAL CHANNEL) or any other of the fixed channels (SMP, ATT...)". The device ends up trying to disconnect a fixed channel, which the Bluetooth specification does not allow. NVD's description lists the results as "undefined behavior, including potential assertion failures, crashes, or memory corruption".
NVD scores it 6.5, vector CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H; Zephyr's CNA score is 7.1 (I:L/A:H) with CWE-190 (Integer Overflow or Wraparound). NVD lists Zephyr through 4.1.0 (NVD). The fix is PR 93576, "Add l2cap credit param checks", plus PR 100474 for the 3.7 long-term-support branch.
Check the release, not only the list entry. The Zephyr 2025 vulnerability list says the issue "has been fixed in main for v4.2.0", but PR 93576 was merged on 2025-08-01, after v4.2.0 was tagged on 2025-07-19. GitHub's tag comparison shows that v4.2.0 and v4.2.1 do not contain the commit and v4.3.0, released 2025-11-13, does. The 3.7 backport was merged on 2026-02-23 and is in v3.7.2, released 2026-03-31. A device on Zephyr 4.2.x needs v4.3.0 or a cherry-pick, even though the list entry suggests 4.2.0 is enough.
Zephyr is the BLE host stack in many peripherals, and the SweynTooth disclosure already tested "Nordic Semiconductor (Zephyr Project Stack) nRF51/52" parts, so the bug ships inside device firmware wherever CONFIG_BT is enabled. The GHSA also says CVE-2025-10457, unchecked connection responses, combines with this bug to cause state confusion.
The CVE is not in the CISA KEV catalog as of 2026-11-16 (catalog version 2026.11.13). FIRST EPSS gives it 0.00211, the 11.4th percentile, in the 2026-11-15 dataset (CISA KEV, FIRST EPSS).
Move Bluetooth-enabled Zephyr products to v4.3.0 or later, or to v3.7.2 on the LTS line, and rebuild the firmware. Our Bluetooth LE security guide covers BLE stack CVEs, our memory corruption fix guide covers integer overflow bugs, and CVE-2025-7403 is the related Zephyr transmit-path use-after-free.
Evidence
- le_credits overflow sends a disconnection request without checking for fixed CIDs (SMP, ATT); remote crash or DoS; published 2025-09-19; patches PR 93576 (main) and PR 100474 (v3.7); CNA 7.1, CWE-190. — Zephyr GHSA-hcc8-3qr7-c9m8
- NVD CVSS 3.1 6.5 (AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H); CNA 7.1; Zephyr through 4.1.0; undefined behavior incl. assertion failures, crashes, memory corruption. — NVD
- Listed as fixed in main for v4.2.0 by PR 93576, with PR 100474 for 3.7. — Zephyr Project 2025 vulnerabilities
- PR 93576 merged 2025-08-01; GitHub compare: not in v4.2.0 (2025-07-19) or v4.2.1, contained in v4.3.0 (2025-11-13). — Zephyr PR 93576
- PR 100474 (v3.7-branch backport) merged 2026-02-23; contained in v3.7.2 (2026-03-31). — Zephyr PR 100474
- Not in the CISA KEV catalog as of 2026-11-16 (catalog version 2026.11.13). — CISA KEV
- EPSS 0.00211 (11.4th percentile), dataset 2026-11-15, read 2026-11-16. — FIRST EPSS

Related advisories
Sources
Frequently asked questions
Which Zephyr release fixes CVE-2025-10456?
v4.3.0 (2025-11-13) on the main line and v3.7.2 (2026-03-31) on the 3.7 LTS line. The Zephyr list says v4.2.0, but the fix was merged on 2025-08-01, after v4.2.0 was tagged (per GitHub PRs 93576 and 100474 and the tag comparison).
What does an attacker achieve with CVE-2025-10456?
A device in radio range can send crafted L2CAP credit indications that make the target try to disconnect a fixed channel, leading to assertion failures, crashes or possibly memory corruption (per NVD and GHSA-hcc8-3qr7-c9m8).
Is CVE-2025-10456 related to CVE-2025-10457?
Yes. Zephyr's advisory for CVE-2025-10457 says the unchecked connection-response handling causes state confusion when combined with this flaw (per GHSA-xqj6-vh76-2vv8).
Is CVE-2025-10456 exploited?
It is not in the CISA KEV catalog as of 2026-11-16 (catalog version 2026.11.13). FIRST EPSS gives it 0.00211, the 11.4th percentile, in the 2026-11-15 dataset (per CISA KEV and FIRST EPSS).
Questions about this page?