Permanent service hang via zero SDIO block size
Published Sep 14, 2026 · Updated Sep 14, 2026
Denial of service in Zephyr RTOS 3.6.0 through 4.4.1 allows physically proximate attackers to hang SDIO-dependent services. The byte-I/O loop in sdio_io_rw_extended_helper() uses an unvalidated card-supplied maximum block size as its step, so zero leaves the remaining length unchanged while the card mutex stays locked. Exploitation requires a removable SDIO or combo card that supplies the malformed CIS value, and recovery requires resetting the device.
Summary
What happened
Denial of service in Zephyr RTOS 3.6.0 through 4.4.1 allows physically proximate attackers to hang SDIO-dependent services. The byte-I/O loop in sdio_io_rw_extended_helper() uses an unvalidated card-supplied maximum block size as its step, so zero leaves the remaining length unchanged while the card mutex stays locked. Exploitation requires a removable SDIO or combo card that supplies the malformed CIS value, and recovery requires resetting the device.
The record
- CVE
- CVE-2026-15923
- Published
- Sep 14, 2026
- Updated
- Sep 14, 2026
- Vendor
- Zephyr Project
- Product
- Zephyr RTOS
- Classifications
- Unavailable
- Attack vector
- physical
- Privileges
- Unavailable
Timeline
How it unfolded
- Sep 14, 2026CVE publishedPublication date reported by the CVE source.
- Sep 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=3.6.0 <4.4.2
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
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
No sourced classifications are available.
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