Bluetooth host crash via zero ACL MTU
Published Feb 26, 2023 · Updated Mar 11, 2025
Improper HCI initialization in Zephyr RTOS 2.4 and earlier allows attackers controlling the Bluetooth controller to crash the host stack. When a non-BR/EDR controller reports a zero ACL MTU, hci_init leaves bt_dev.le.acl_pkts uninitialized instead of rejecting startup. The flaw requires CONFIG_BT_CONN with BR/EDR disabled and a controller that supplies the zero length; ordinary Bluetooth traffic then dereferences the uninitialized semaphore.
Summary
What happened
Improper HCI initialization in Zephyr RTOS 2.4 and earlier allows attackers controlling the Bluetooth controller to crash the host stack. When a non-BR/EDR controller reports a zero ACL MTU, hci_init leaves bt_dev.le.acl_pkts uninitialized instead of rejecting startup. The flaw requires CONFIG_BT_CONN with BR/EDR disabled and a controller that supplies the zero length; ordinary Bluetooth traffic then dereferences the uninitialized semaphore.
The record
- CVE
- CVE-2021-3329
- Published
- Feb 26, 2023
- Updated
- Mar 11, 2025
- Vendor
- Zephyr Project
- Product
- Zephyr RTOS
- Classifications
- CWE-665, CWE-703, T1499
- Attack vector
- adjacent
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 26, 2023CVE publishedPublication date reported by the CVE source.
- Mar 11, 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 <=v2.4
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
- Zero ACL MTU crash reproduction procedureproof of concept · demonstrated
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