CVE-2026-93669: NULL pointer dereference in the ITE IT8xxx2 SHI host-command backend when a host transaction arrives before backend initialization

Published Nov 16, 2026
·
Updated

The ITE IT8xxx2 SHI host-command backend in subsys/mgmt/echostcmd/backends/echostcmdbackendshiite.c arms the SPI peripheral before its receive context exists. shiiteinitregisters() sets the state machine to SHISTATEREADYTORECV and calls irqenable() while the device initializes at POSTKERNEL priority CONFIGKERNELINITPRIORITYDEFAULT (40), but data->rxctx and data->tx are only assigned later by shiitebackendinit(), which echostcmdinit() invokes at CONFIGECHOSTCMDINITPRIORITY (default 80).

If the attached host processor starts a SPI transaction inside that window, the Rx-valid-length interrupt fires, shiiteinthandler() passes its state check and calls shiiteparseheader(), which stores the host-derived request length through the still-NULL data->rxctx. On the IT8xxx2 low addresses are not backed by RAM, and with CONFIGNULLPOINTEREXCEPTIONDETECTIONPMP 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 CONFIGECHOSTCMDINITIALIZEATBOOT is disabled and the application calls echostcmdinit() 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 SHISTATEDISABLED with the interrupt masked during device init, moves irqenable() into shiitebackendinit() after the buffers are published, and makes shiiteinthandler() reject a NULL data->rxctx while write-clearing IT83XXSPIISR and IT83XXSPIRXVLISR so that an unexpected early interrupt cannot storm.

Affected Software

1 affected component
Zephyr Project Zephyr

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Compensating control

    In the ITE IT8xxx2 SHI backend, keep the interface at SHI_STATE_DISABLED with the interrupt masked during device initialization, and call irq_enable() in shi_ite_backend_init() only after the receive and transmit buffers are published.

  2. Compensating control

    In shi_ite_int_handler(), reject a NULL data->rx_ctx and write-clear IT83XX_SPI_ISR and IT83XX_SPI_RX_VLISR to prevent an unexpected early interrupt from causing a fault or interrupt storm.

Event History

Nov 16, 2026
CVE Published
via MITRE·09:19 PM
Data Sourced
via MITRE·09:19 PM
DescriptionSeverityWeakness

Frequently Asked Questions

1

Which systems are exposed to the initialization race?

Systems using the ITE IT8xxx2 SHI host-command backend are exposed if an attached host processor can begin an SPI transaction before ec_host_cmd_init() has run shi_ite_backend_init(). The normal initialization ordering creates a window because the SHI peripheral is enabled at priority 40 while host-command backend setup defaults to priority 80.

2

What must happen for the fault to be triggered?

The attached host must start an SPI transaction during the window before data->rx_ctx and data->tx are assigned. The receive-valid-length interrupt must then reach header parsing, which writes the host-provided request length through the NULL receive-context pointer.

3

Does the configuration make the exposure window larger?

Yes. Disabling CONFIG_EC_HOST_CMD_INITIALIZE_AT_BOOT can widen the window because initialization is then delayed until the application explicitly calls ec_host_cmd_init().

4

What is the practical impact when the issue is triggered?

The NULL-pointer write can raise a fatal access fault in interrupt context and cause a kernel panic. This is especially explicit with CONFIG_NULL_POINTER_EXCEPTION_DETECTION_PMP, which makes the first bytes of the address space inaccessible.

5

What can be done if an update cannot be applied immediately?

Prevent the attached host from issuing SHI SPI transactions until the host-command backend has been initialized. Avoid configurations that delay ec_host_cmd_init(), including disabling CONFIG_EC_HOST_CMD_INITIALIZE_AT_BOOT, where possible.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203