# CVE-2026-93669 — zephyrproject zephyr

> As of 2026-11-17, CVE-2026-93669 is a MEDIUM-severity vulnerability in zephyrproject zephyr, CVSS v3.1 4.7, EPSS 0.0% (54.7th percentile). No Threadlinqs-tracked threat campaign has been attributed to CVE-2026-93669 as of 2026-11-17; the identifier is re-checked against the Threadlinqs threat corpus on every daily ingest.

**Last updated:** 2026-11-17

## What is CVE-2026-93669?

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.

The record classifies CVE-2026-93669 under weakness class [CWE-476](https://intel.threadlinqs.com/cwe/CWE-476). Its CVSS v3 base vector states that the flaw requires local access to the host, needs low-privilege credentials, needs no user interaction, and has high impact on availability. 1 affected-product entry is recorded, across 1 vendor, listed below. The identifier was first published 3 days ago.

## Severity and exploitation probability

- **CVSS v3.1 base score:** 4.7 — MEDIUM (`CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H`)
- **EPSS (FIRST):** 0.0% probability of exploitation in the next 30 days, higher than 54.7% of all scored CVEs
- **CISA KEV:** Not listed in the CISA Known Exploited Vulnerabilities catalog
- **Threadlinqs priority:** 4.5/10 — a Threadlinqs composite of the CVSS base score, the EPSS percentile and public exploit availability
- **Published:** 2026-11-16

## Is CVE-2026-93669 being exploited?

It currently carries a trending score of 43 in the Threadlinqs vulnerability feed.

## Affected products and versions

- [zephyrproject](https://intel.threadlinqs.com/vendors/zephyrproject): zephyr

## How to fix CVE-2026-93669

Patch reference: [https://github.com/zephyrproject-rtos/zephyr/commit/73c6a4ed9506ca81ddfb9d89197b74425a8ce632](https://github.com/zephyrproject-rtos/zephyr/commit/73c6a4ed9506ca81ddfb9d89197b74425a8ce632). Apply the vendor fix referenced above to every affected product listed in this record, then confirm the running version against the vendor advisory.

## Threat activity tracking CVE-2026-93669

No threat campaign in the Threadlinqs corpus currently references CVE-2026-93669, in its CVE list or as an indicator. The linkage is recomputed from the live corpus on every daily ingest, so this section fills in as soon as a tracked campaign cites the identifier.

## Sources

Enriched from CVE.org, NVD, FIRST EPSS. This product uses the NVD API but is not endorsed or certified by the NVD.

**Vendor advisory and patch**

- [github.com — patch](https://github.com/zephyrproject-rtos/zephyr/commit/73c6a4ed9506ca81ddfb9d89197b74425a8ce632)

**Other references**

- [github.com](https://github.com/zephyrproject-rtos/zephyr/security/advisories/GHSA-xqxg-8rx7-42hq)

Canonical: https://intel.threadlinqs.com/cve/CVE-2026-93669
No Threadlinqs detection currently covers CVE-2026-93669; it is re-checked on every ingest.
Indicator values unlock with TL Creds (https://threadlinqs.com/tl-creds); MCP access for AI agents needs Purple: https://intel.threadlinqs.com/mcp
