Bluetooth service interruption via wrapped L2CAP length
Published Dec 15, 2025 · Updated Dec 15, 2025
Integer overflow in Zephyr RTOS 4.2 and earlier allows physically proximate attackers to interrupt Bluetooth Classic traffic. Within bt_br_acl_recv, an attacker-controlled 0xfffc L2CAP length plus the four-byte header wraps a 16-bit total to zero, clipping the receive buffer to zero while payload remains. BR/EDR must be enabled, and sustained malformed traffic can desynchronize flow control, exhaust CPU resources, or force a watchdog reset; memory corruption is not reported.
Summary
What happened
Integer overflow in Zephyr RTOS 4.2 and earlier allows physically proximate attackers to interrupt Bluetooth Classic traffic. Within bt_br_acl_recv, an attacker-controlled 0xfffc L2CAP length plus the four-byte header wraps a 16-bit total to zero, clipping the receive buffer to zero while payload remains. BR/EDR must be enabled, and sustained malformed traffic can desynchronize flow control, exhaust CPU resources, or force a watchdog reset; memory corruption is not reported.
The record
- CVE
- CVE-2025-12035
- Published
- Dec 15, 2025
- Updated
- Dec 15, 2025
- Vendor
- Zephyr Project
- Product
- Zephyr RTOS
- Classifications
- CWE-190, T1499.002
- Attack vector
- adjacent
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 15, 2025CVE publishedPublication date reported by the CVE source.
- Dec 15, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=* <=4.2
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo