Firmware-update interruption via unsynchronized shared context
Published Aug 10, 2026 · Updated Aug 10, 2026
Race condition in UpdateHub in Zephyr RTOS 2.0.0 through 4.4.1 allows local users to interrupt firmware updates via concurrent operations. The subsystem shares one file-scope context without locking, so concurrent flows can make prepare_fds write past fds[1] into adjacent socket state. Triggering requires permission to invoke an update operation and winning a race against the background handler; the demonstrated consequence is update-path state corruption and denial of service.
Summary
What happened
Race condition in UpdateHub in Zephyr RTOS 2.0.0 through 4.4.1 allows local users to interrupt firmware updates via concurrent operations. The subsystem shares one file-scope context without locking, so concurrent flows can make prepare_fds write past fds[1] into adjacent socket state. Triggering requires permission to invoke an update operation and winning a race against the background handler; the demonstrated consequence is update-path state corruption and denial of service.
The record
- CVE
- CVE-2026-11812
- Published
- Aug 10, 2026
- Updated
- Aug 10, 2026
- Vendor
- Zephyr Project
- Product
- Zephyr RTOS
- Classifications
- CWE-362, T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 10, 2026CVE publishedPublication date reported by the CVE source.
- Aug 10, 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=2.0.0 <=4.4.1
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