Device hang via ISR scheduler yield
Published Mar 14, 2026 · Updated Mar 14, 2026
Infinite-loop DoS in Zephyr RTOS 4.3 and earlier allows local users to hang STM32 devices during USB endpoint writes. The usb_write function calls k_yield after an endpoint write returns EAGAIN, even when the STM32 HAL invokes it from an interrupt handler where scheduler yielding is forbidden. Reachability requires STM32 firmware built with the affected USB device stack and code able to provoke the retry path; execution can remain stuck until the device is reset.
Summary
What happened
Infinite-loop DoS in Zephyr RTOS 4.3 and earlier allows local users to hang STM32 devices during USB endpoint writes. The usb_write function calls k_yield after an endpoint write returns EAGAIN, even when the STM32 HAL invokes it from an interrupt handler where scheduler yielding is forbidden. Reachability requires STM32 firmware built with the affected USB device stack and code able to provoke the retry path; execution can remain stuck until the device is reset.
The record
- CVE
- CVE-2026-4179
- Published
- Mar 14, 2026
- Updated
- Mar 14, 2026
- Vendor
- Zephyr Project
- Product
- Zephyr RTOS
- Classifications
- CWE-835, T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 14, 2026CVE publishedPublication date reported by the CVE source.
- Mar 14, 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.3
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
- STM32 USB mass-storage reproducerproof 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