Device crash via null DFU download buffer
Published Aug 11, 2026 · Updated Aug 11, 2026
NULL pointer dereference in USB DFU in Zephyr RTOS 4.4.0 through 4.4.2 allows physically proximate attackers to crash devices. The device_next handle_download() path dereferences buf->len and buf->data when a zero-length DFU_DNLOAD request reaches it without a Data OUT buffer. Exploitation requires enabled DFU download support, a registered image, and a prior transition to DFU_DNLOAD_IDLE; the consequence is limited to device availability.
Summary
What happened
NULL pointer dereference in USB DFU in Zephyr RTOS 4.4.0 through 4.4.2 allows physically proximate attackers to crash devices. The device_next handle_download() path dereferences buf->len and buf->data when a zero-length DFU_DNLOAD request reaches it without a Data OUT buffer. Exploitation requires enabled DFU download support, a registered image, and a prior transition to DFU_DNLOAD_IDLE; the consequence is limited to device availability.
The record
- CVE
- CVE-2026-12051
- Published
- Aug 11, 2026
- Updated
- Aug 11, 2026
- Vendor
- Zephyr Project
- Product
- Zephyr RTOS
- Classifications
- CWE-476, T1499
- Attack vector
- physical
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 11, 2026CVE publishedPublication date reported by the CVE source.
- Aug 11, 2026Record 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=4.4.0 <4.5.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.
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