CVE-2025-7403 Details
Description
Unsafe handling in bt_conn_tx_processor causes a use-after-free, resulting in a write-before-zero. The written 4 bytes are attacker-controlled, enabling precise memory corruption.
A use-after-free vulnerability has been identified in the Bluetooth connection transmission processor of Zephyr versions through 4.1. This issue arises from improper management of network buffers holding ACL transmission data. When a Bluetooth disconnection occurs, the processor deallocates these buffers without considering that the data may be segmented. This oversight leads to a write-before-zero condition, where the freed buffer is reused and written to, allowing an attacker to manipulate the written bytes and cause precise memory corruption. Such exploitation could form the basis of a reliable remote attack.
Users can refer to the Zephyr GitHub repository for information on the vulnerability and potential patches. As of now, there is no official patched version available.
Metrics
CVSS 4.0 Severity and Vector Strings:
No CVSS 4.0 data is available for this CVE.
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
CISA-ADP
Assessed Sep 19, 2025References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
| URL | Source(s) | Tag(s) |
|---|---|---|
| https://github.com/zephyrproject-rtos/zephyr/security/advisories/GHSA-9r46-cqqw-6j2j | [email protected] | PatchVendor Advisory |
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| CWE-123 | Write-what-where Condition | [email protected] |
Affected Products
| Product | Versions |
|---|---|
| zephyrproject zephyr | <= 4.1.0 |
CPE
Remediation
| |
Change History
4 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Jun 17, 2026 | CVE Modified | [email protected] |
| Jun 17, 2026 | CVE Modified | CISA-ADP |
| Oct 29, 2025 | Initial Analysis | [email protected] |
| Sep 19, 2025 | New CVE Received | [email protected] |