SEPTEMBER 7, 2026
Live Feed
Back to database
Case File

CVE-2026-10679

LOW · CVSS 3.3 EPSS 0.13% Public Exploit

Source: NVD + CISA KEV + EPSS · Published 2026-07-21 · Last synced 2026-08-20

CyberRota Analysis

AI-Generated

The DesignWare SPI driver in Zephyr is vulnerable due to insufficient validation of the frequency parameter, allowing a userspace thread to trigger a divide-by-zero error, which results in a kernel fault and local denial of service. This issue affects all Zephyr releases up to v4.4.0 and requires CONFIG_USERSPACE enabled, along with an unprivileged thread having SPI driver access. Organizations using affected versions of Zephyr with user-space capabilities should prioritize applying the fix to mitigate potential service disruptions.

Public Exploit Signal

A public exploit, PoC, GitHub repository or Metasploit reference was detected for this CVE.

Detected Signals
exploit

Note: these links are listed for security research and verification purposes only.

CVE
CVE-2026-10679
Severity
LOW
CVSS
3.3
EPSS
0.13%

Original NVD Description

The DesignWare SPI driver (drivers/spi/spi_dw.c) computed the SPI BAUDR clock divider as info->clock_frequency / config->frequency without validating config->frequency. spi_transceive is a Zephyr __syscall and its verify handler (drivers/spi/spi_handlers.c) copies the caller-supplied spi_config from userspace without checking the frequency field, so a userspace thread that has been granted access to a DesignWare SPI device kernel object can pass frequency = 0 and trigger an unsigned integer divide-by-zero in spi_dw_configure(). On Cortex-M Mainline (SCB->CCR.DIV_0_TRP is set in z_arm_fault_init()) and on ARC (a dedicated __ev_div_zero vector) this raises a CPU exception, resulting in a kernel fault and local denial of service. The fix rejects zero frequency and frequencies above clock_frequency / 2 (the DesignWare SSI databook minimum SCKDIV of 2) with -EINVAL. The defect affects all Zephyr releases up to and including v4.4.0; exploitation requires CONFIG_USERSPACE=y and an unprivileged thread already granted SPI driver permission. There is no memory-corruption or information-disclosure impact.

Related CVEs

Other vulnerabilities affecting the same vendor(s)