Device halt via mismatched UART syscall checks
Published Nov 10, 2026 · Updated Nov 10, 2026
NULL calls in Zephyr RTOS UART syscalls allow local users to halt or reboot the device through wide-data operations. The verifiers in drivers/serial/uart_handlers.c validate the 8-bit poll_out, tx, and rx_enable operations instead of their 16-bit counterparts, allowing kernel implementations to call NULL driver pointers. Exploitation requires CONFIG_USERSPACE, CONFIG_UART_WIDE_DATA, permission to access a UART device lacking the corresponding 16-bit operation, and CONFIG_UART_ASYNC_API for asynchronous calls; the default fatal handler halts the system or warm-reboots it when configured, without attacker-controlled code execution or memory disclosure.
Summary
What happened
NULL calls in Zephyr RTOS UART syscalls allow local users to halt or reboot the device through wide-data operations. The verifiers in drivers/serial/uart_handlers.c validate the 8-bit poll_out, tx, and rx_enable operations instead of their 16-bit counterparts, allowing kernel implementations to call NULL driver pointers. Exploitation requires CONFIG_USERSPACE, CONFIG_UART_WIDE_DATA, permission to access a UART device lacking the corresponding 16-bit operation, and CONFIG_UART_ASYNC_API for asynchronous calls; the default fatal handler halts the system or warm-reboots it when configured, without attacker-controlled code execution or memory disclosure.
The record
- CVE
- CVE-2026-90834
- Published
- Nov 10, 2026
- Updated
- Nov 10, 2026
- Vendor
- Zephyr Project
- Product
- Zephyr RTOS
- Classifications
- T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Nov 10, 2026CVE publishedPublication date reported by the CVE source.
- Nov 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=3.0.0 <4.3.2
- Affected versionversion=4.4.0 <4.5.0
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.
Activity data is delayed. The latest report is Sep 28, 2026.
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
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Contact us