Heap corruption via unchecked USB HCI appends
Published Jan 11, 2023 · Updated Apr 9, 2025
Heap-based buffer overflow in Zephyr RTOS before 3.0.0 allows physically proximate attackers to corrupt memory via crafted USB HCI data. The acl_read_cb function repeatedly passes attacker-controlled HCI OUT chunks to net_buf_add_mem without checking the fixed-size buffer tailroom. A connected USB host can overflow heap memory, causing a crash, security-feature bypass, or arbitrary code execution.
Summary
What happened
Heap-based buffer overflow in Zephyr RTOS before 3.0.0 allows physically proximate attackers to corrupt memory via crafted USB HCI data. The acl_read_cb function repeatedly passes attacker-controlled HCI OUT chunks to net_buf_add_mem without checking the fixed-size buffer tailroom. A connected USB host can overflow heap memory, causing a crash, security-feature bypass, or arbitrary code execution.
The record
- CVE
- CVE-2021-3966
- Published
- Jan 11, 2023
- Updated
- Apr 9, 2025
- Vendor
- Zephyr Project
- Product
- Zephyr RTOS
- Classifications
- CWE-122, CWE-120, T1203
- Attack vector
- adjacent
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 11, 2023CVE publishedPublication date reported by the CVE source.
- Apr 9, 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.0
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