Bluetooth controller deadlock via unreleased RX node
Published Jun 28, 2022 · Updated Sep 16, 2024
Improper exception handling in Zephyr RTOS 2.5.0 allows physically proximate attackers to deadlock the Bluetooth controller via CONNECT_IND. The Bluetooth Link Layer handler rejects an invalid channel map without releasing the RX node reserved for connection-complete and CSA#2 events. A crafted Bluetooth Low Energy connection request within radio range leaks that finite controller buffer and stalls further operation.
Summary
What happened
Improper exception handling in Zephyr RTOS 2.5.0 allows physically proximate attackers to deadlock the Bluetooth controller via CONNECT_IND. The Bluetooth Link Layer handler rejects an invalid channel map without releasing the RX node reserved for connection-complete and CSA#2 events. A crafted Bluetooth Low Energy connection request within radio range leaks that finite controller buffer and stalls further operation.
The record
- CVE
- CVE-2021-3433
- Published
- Jun 28, 2022
- Updated
- Sep 16, 2024
- Vendor
- Zephyr Project
- Product
- Zephyr RTOS
- Classifications
- CWE-703, T1499.004
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 28, 2022CVE publishedPublication date reported by the CVE source.
- Sep 16, 2024Record 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=v2.5.0 <unspecified
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