CVE-2025-7403 is a use-after-free in the Bluetooth host of the Zephyr RTOS: after an LE disconnection, bt_conn_tx_processor frees transmit buffers that segmented L2CAP data still uses, and a later write puts 4 attacker-controlled bytes into freed memory. NVD scores it 6.5 for Zephyr through 4.1.0; Zephyr v4.2.0 contains the fix.
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-7403 · Source: NVD
Affected components
| Component | CPE | Version range |
|---|---|---|
| Zephyr RTOS Bluetooth host (bt_conn_tx_processor, l2cap_pull_data) | cpe:2.3:o:zephyrproject:zephyr:*:*:*:*:*:*:*:* | through 4.1.0 (NVD); fixed by PR 90975, merged 2025-07-03, included in v4.2.0 (2025-07-19) |
What does this mean for affected devices?
Zephyr's security team published CVE-2025-7403 as GHSA-9r46-cqqw-6j2j on 2025-09-19; the advisory gives an embargo date of 2025-09-05. The advisory walks through the bug: bt_conn_tx_processor releases the network buffers holding queued ACL data when an LE connection drops, but l2cap_pull_data segments a PDU into several K-frames and only pops it from the channel queue after the last segment. The processor "assumes that returned pointer can be UNREFED (freed)", which leads to "a write-before-zero when the next segment send is acknowledged". The advisory adds that the 4 bytes written "are highly controlled by outside attacker and this can form the basis of a reliable exploit".
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, an availability-only rating. Zephyr, as the CNA, scores it 7.6 (C:L/I:L/A:H) and assigns CWE-123 (Write-what-where Condition). NVD's configuration covers Zephyr through 4.1.0 (NVD). The Zephyr 2025 vulnerability list gives the fix as PR 90975 for main, "fixed in main for v4.2.0". The PR was merged on 2025-07-03 and GitHub's tag comparison places it inside v4.2.0, released 2025-07-19. Zephyr's list names no backport to the 3.7 long-term-support branch for this CVE.
Zephyr is the host stack on a wide range of BLE chips, so the code reaches devices as part of each product's firmware image, and the SweynTooth disclosure already listed "Nordic Semiconductor (Zephyr Project Stack) nRF51/52" among the stacks it tested. A product built on a Zephyr release before 4.2.0 with Bluetooth enabled carries this code until the maker rebuilds and ships new firmware.
The CVE is not in the CISA KEV catalog as of 2026-11-16 (catalog version 2026.11.13). FIRST EPSS gives it 0.00208, the 10.9th percentile, in the 2026-11-15 dataset (CISA KEV, FIRST EPSS).
Check the Zephyr version in your build manifest and whether CONFIG_BT is set; then move to v4.2.0 or later, or cherry-pick PR 90975 onto your tree. Our Bluetooth LE security guide explains why the BLE stack is a versioned component to track, and our firmware SBOM guide shows how to record it. The other Zephyr Bluetooth flaws from the same disclosure are CVE-2025-10456 and CVE-2025-10457.
Evidence
- bt_conn_tx_processor frees ACL TX net_bufs on disconnect; l2cap_pull_data segments K-frames; write-before-zero with attacker-controlled 4 bytes; published 2025-09-19; embargo 2025-09-05; CNA 7.6, CWE-123; fix PR 90975. — Zephyr GHSA-9r46-cqqw-6j2j
- NVD CVSS 3.1 6.5 (AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H); Zephyr CNA 7.6; CWE-123; Zephyr through 4.1.0. — NVD
- Fixed in main for v4.2.0 by PR 90975; no other branch listed. — Zephyr Project 2025 vulnerabilities
- PR 90975 merged 2025-07-03; contained in tag v4.2.0 (released 2025-07-19) per GitHub compare. — Zephyr PR 90975
- 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.00208 (10.9th percentile), dataset 2026-11-15, read 2026-11-16. — FIRST EPSS

Related advisories
Sources
Frequently asked questions
Which Zephyr versions fix CVE-2025-7403?
Zephyr v4.2.0, released 2025-07-19, contains the fix (PR 90975, merged 2025-07-03). NVD lists Zephyr through 4.1.0 as affected, and Zephyr's list names no 3.7 LTS backport (per NVD, the Zephyr vulnerability list and GitHub).
Why do NVD and Zephyr score CVE-2025-7403 differently?
NVD rates only availability impact (6.5, A:H). Zephyr's CNA score of 7.6 also counts low confidentiality and integrity impact, because the freed buffer is written with attacker-controlled bytes (per NVD and GHSA-9r46-cqqw-6j2j).
Can CVE-2025-7403 be reached over the air?
Yes. The vector is adjacent network with no privileges or user interaction: the flaw is triggered through an LE connection and its disconnection while segmented L2CAP data is queued (per NVD and the Zephyr advisory).
Is CVE-2025-7403 exploited?
It is not in the CISA KEV catalog as of 2026-11-16 (catalog version 2026.11.13). FIRST EPSS gives it 0.00208, the 10.9th percentile, in the 2026-11-15 dataset (per CISA KEV and FIRST EPSS).
Questions about this page?