CVE-2026-93669
Awaiting Analysis Awaiting Analysis - Queue

Kernel Panic in ITE IT8xxx2 EC Host Command Interface

Vulnerability report for CVE-2026-93669, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-11-16

Last updated on: 2026-11-16

Assigner: Zephyr Project

Description

The ITE IT8xxx2 SHI host-command backend in subsys/mgmt/ec_host_cmd/backends/ec_host_cmd_backend_shi_ite.c arms the SPI peripheral before its receive context exists. shi_ite_init_registers() sets the state machine to SHI_STATE_READY_TO_RECV and calls irq_enable() while the device initializes at POST_KERNEL priority CONFIG_KERNEL_INIT_PRIORITY_DEFAULT (40), but data->rx_ctx and data->tx are only assigned later by shi_ite_backend_init(), which ec_host_cmd_init() invokes at CONFIG_EC_HOST_CMD_INIT_PRIORITY (default 80). If the attached host processor starts a SPI transaction inside that window, the Rx-valid-length interrupt fires, shi_ite_int_handler() passes its state check and calls shi_ite_parse_header(), which stores the host-derived request length through the still-NULL data->rx_ctx. On the IT8xxx2 low addresses are not backed by RAM, and with CONFIG_NULL_POINTER_EXCEPTION_DETECTION_PMP the first bytes of the address space are explicitly made inaccessible, so the store raises a fatal access fault in interrupt context. The window widens further when CONFIG_EC_HOST_CMD_INITIALIZE_AT_BOOT is disabled and the application calls ec_host_cmd_init() itself. The result is a kernel panic on the embedded controller: with Zephyr's default fatal handler the CPU halts, so the controller stops servicing host commands until a hardware reset. Because the trigger is traffic from the attached host processor -- an untrusted peer from the controller firmware's point of view -- software on that host can provoke the fault by forcing a controller reset and issuing transactions during the reboot, turning a recoverable reset into a persistent outage. Impact is limited to availability: the faulting address is fixed and not attacker-chosen, so no memory-corruption primitive follows. The fix leaves the interface at SHI_STATE_DISABLED with the interrupt masked during device init, moves irq_enable() into shi_ite_backend_init() after the buffers are published, and makes shi_ite_int_handler() reject a NULL data->rx_ctx while write-clearing IT83XX_SPI_ISR and IT83XX_SPI_RX_VLISR so that an unexpected early interrupt cannot storm.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-11-16
Last Modified
2026-11-16
Generated
2026-11-17
AI Q&A
2026-11-17
EPSS Evaluated
N/A
NVD
EUVD

Affected Vendors & Products

Showing 2 associated CPEs
Vendor Product Version / Range
zephyrproject zephyr From 3.4.0 (inc) to 4.3.2 (exc)
zephyrproject zephyr From 4.4.0 (inc) to 4.5.0 (exc)

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-476 The product dereferences a pointer that it expects to be valid but is NULL.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This is a kernel panic vulnerability in the ITE IT8xxx2 SHI host-command backend for Zephyr RTOS. It occurs when the SPI peripheral is armed before its receive context is initialized, causing a NULL pointer dereference during an interrupt handler. The issue stems from a race condition where the device state is set to ready before buffers are assigned, leading to a fatal access fault when the host processor initiates a SPI transaction during this window.

Detection Guidance

This vulnerability is specific to embedded systems using the ITE IT8xxx2 EC host command backend in Zephyr RTOS. Detection requires checking for kernel panics or fatal access faults during SPI transactions, particularly during device initialization. Monitor logs for fatal errors or watchdog resets during boot sequences.

Impact Analysis

The vulnerability can cause the embedded controller to crash and stop servicing host commands until a hardware reset. An attacker controlling the host processor can repeatedly trigger this fault by forcing resets and sending transactions during reboot, turning temporary crashes into persistent outages. The impact is limited to availability as the faulting address is fixed and not attacker-controlled.

Mitigation Strategies

Apply the provided fix by ensuring the SHI interface remains disabled with interrupts masked during device initialization. Move irq_enable() to after buffer initialization in shi_ite_backend_init(). Update the interrupt handler to reject NULL data->rx_ctx and clear pending interrupts.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-93669. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart

Security Radar

News mentioning this vulnerability
Loading related security news...