Device crash via unchecked Bluetooth subgroup count
Published Sep 13, 2024 · Updated Sep 17, 2025
Stack-based buffer overflow in Zephyr RTOS 3.6 and earlier allows physically proximate attackers to crash devices via Bluetooth. parse_recv_state trusts the received num_subgroups byte as a loop bound and indexes beyond its fixed-size subgroups array on the read_recv_state_cb stack. Exploitation requires Bluetooth adjacency and a crafted Broadcast Audio Scan Service receive state; the published impact is device instability or a crash.
Summary
What happened
Stack-based buffer overflow in Zephyr RTOS 3.6 and earlier allows physically proximate attackers to crash devices via Bluetooth. parse_recv_state trusts the received num_subgroups byte as a loop bound and indexes beyond its fixed-size subgroups array on the read_recv_state_cb stack. Exploitation requires Bluetooth adjacency and a crafted Broadcast Audio Scan Service receive state; the published impact is device instability or a crash.
The record
- CVE
- CVE-2024-5931
- Published
- Sep 13, 2024
- Updated
- Sep 17, 2025
- Vendor
- Zephyr Project
- Product
- Zephyr RTOS
- Classifications
- CWE-1284, CWE-121, T1499.004
- Attack vector
- adjacent
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 13, 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=0 <=3.6
- Affected versionversion=* <=3.6
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