Device crash via unchecked AVDTP buffer pull
Published Dec 15, 2024 · Updated Sep 17, 2025
Heap buffer overflow in Zephyr RTOS 3.7 and earlier allows remote attackers to crash devices through malformed Bluetooth AVDTP packets. bt_avdtp_l2cap_recv pulls the signal identifier and remaining body from a net_buf without first confirming that the buffer contains the required bytes. Unauthenticated Bluetooth reachability is sufficient, and the documented consequence is device instability or a denial-of-service crash.
Summary
What happened
Heap buffer overflow in Zephyr RTOS 3.7 and earlier allows remote attackers to crash devices through malformed Bluetooth AVDTP packets. bt_avdtp_l2cap_recv pulls the signal identifier and remaining body from a net_buf without first confirming that the buffer contains the required bytes. Unauthenticated Bluetooth reachability is sufficient, and the documented consequence is device instability or a denial-of-service crash.
The record
- CVE
- CVE-2024-8798
- Published
- Dec 15, 2024
- Updated
- Sep 17, 2025
- Vendor
- Zephyr Project
- Product
- Zephyr RTOS
- Classifications
- CWE-787, CWE-122, T1499
- Attack vector
- adjacent
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 15, 2024CVE publishedPublication date reported by the CVE source.
- Sep 17, 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=* <=3.7
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.
Weakness, pattern, technique
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