---
id: "CVE-2026-93669"
page: "https://infrastack.ai/live/CVE-2026-93669"
kind: "vulnerability"
aliases: ["CVE-2026-93669"]
title: "Zephyr: early SPI interrupt on IT8xxx2 EC causes controller kernel panic"
severity: "medium"
cvss: 4.7
epss: null
exploited: false
status: "open"
category: "runtime"
products: []
ecosystems: []
tags: ["ec-host-cmd", "embedded", "ite-it8xxx2", "runtime", "zephyr"]
not_affected_if: ["no-shi-backend", "other-soc"]
published_at: "2026-11-16T22:18:26+00:00"
first_seen_at: "2026-11-16T22:39:16+00:00"
updated_at: "2026-11-16T22:41:13+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-93669", "first_seen_at": "2026-11-16T22:39:16+00:00"}]
exploit_sources: []
---

# Zephyr: early SPI interrupt on IT8xxx2 EC causes controller kernel panic

Link for people: https://infrastack.ai/live/CVE-2026-93669 (this .md is for agents)

The Zephyr host-command SPI backend for the ITE IT8xxx2 embedded controller enables its SPI interrupt before the receive buffers are set up. A host processor that starts an SPI transaction during that window triggers a fatal access fault and halts the controller.

_Summary, check and fix written by a model from the sources; labelled as such._

## How to check

- Check whether the firmware is built on Zephyr with the ITE IT8xxx2 SHI host-command backend (`ec_host_cmd_backend_shi_ite.c`) enabled.
- Check whether `CONFIG_EC_HOST_CMD_INITIALIZE_AT_BOOT` is disabled and the application calls `ec_host_cmd_init()` itself.

## Timeline

- 2026-11-16T22:39:16+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2026-93669

## Documents

- [advisory] Vendor advisory: github.com https://github.com/zephyrproject-rtos/zephyr/security/advisories/GHSA-xqxg-8rx7-42hq
- [fix] Patch: github.com https://github.com/zephyrproject-rtos/zephyr/commit/73c6a4ed9506ca81ddfb9d89197b74425a8ce632

## From the sources

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.

---

_Free to read, with fair use of about 60 pages a minute. For higher limits or API access: sales@infrastack.ai_
