Device crash via HCI buffer double free
Published Jan 19, 2023 · Updated Apr 3, 2025
Double free in Zephyr RTOS 3.2 and earlier allows physically proximate attackers to crash a device through Bluetooth HCI errors. The bt_spi_send and bt_esp32_send error paths release a network buffer even though ownership remains with bt_send's caller, which releases it again. Exploitation requires a compromised radio chip or induced SPI send errors; the demonstrated consequence is a device crash, while further exploitability is unverified.
Summary
What happened
Double free in Zephyr RTOS 3.2 and earlier allows physically proximate attackers to crash a device through Bluetooth HCI errors. The bt_spi_send and bt_esp32_send error paths release a network buffer even though ownership remains with bt_send's caller, which releases it again. Exploitation requires a compromised radio chip or induced SPI send errors; the demonstrated consequence is a device crash, while further exploitability is unverified.
The record
- CVE
- CVE-2022-3806
- Published
- Jan 19, 2023
- Updated
- Apr 3, 2025
- Vendor
- Zephyr Project
- Product
- Zephyr RTOS
- Classifications
- CWE-415, T1499.004
- Attack vector
- physical
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 19, 2023CVE publishedPublication date reported by the CVE source.
- Apr 3, 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=unspecified <=v3.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