CVE-2026-10679

MEDIUMNVD 5.55.5
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 5.5 under NVD CVSS v3. EPSS exploit probability: 0.1%, top 97% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
5.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.5Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
5.5
EG Score
5.5(medium)
EG Risk
25(Track)
EG Risk 25/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity55% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
3%
KEV
Not listed

Published

July 21, 2026

Last Modified

July 30, 2026

Advisory Details (2)

Auto-updated Jul 30, 2026
Patch available. Sources: github_commit, github.
github Patch Available

Divide-by-zero in DesignWare SPI driver reachable from spi_transceive syscall (local DoS) · Advisory · zephyrproject-rtos/zephyr · GitHub

https://github.com/zephyrproject-rtos/zephyr/security/advisories/GHSA-3qcm-qwh2-v4hq
github_commit

commit 65935885622b (zephyrproject-rtos/zephyr)

Fix landed in zephyrproject-rtos/zephyr commit 65935885622b — awaiting tagged release

https://github.com/zephyrproject-rtos/zephyr/commit/65935885622b0e4a5dbe5b82504c30097eb75ce0

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 11× in last 7d / 46× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-09-11 14:52 UTCEPSS rescore
  2. 2026-09-11 09:36 UTCEPSS rescore
  3. 2026-09-11 08:52 UTCEG score recompute
  4. 2026-09-10 09:34 UTCEPSS rescore
  5. 2026-09-09 11:10 UTCEG score recompute
  6. 2026-09-08 22:00 UTCEPSS rescore
  7. 2026-09-07 22:28 UTCEG score recompute
  8. 2026-09-07 16:01 UTCEPSS rescore
  9. 2026-09-06 13:47 UTCEPSS rescore
  10. 2026-09-06 10:39 UTCEG score recompute
  11. 2026-09-05 08:25 UTCEG score recompute
  12. 2026-09-04 05:06 UTCEPSS rescore
  13. 2026-09-02 14:11 UTCEPSS rescore
  14. 2026-09-02 00:55 UTCEG score recompute
  15. 2026-09-01 13:53 UTCEPSS rescore
  16. 2026-09-01 04:39 UTCEPSS rescore
  17. 2026-08-31 02:57 UTCEG score recompute
  18. 2026-08-30 19:17 UTCEPSS rescore
  19. 2026-08-30 02:09 UTCEG score recompute
  20. 2026-08-30 01:21 UTCEPSS rescore
  21. 2026-08-28 21:40 UTCEPSS rescore
  22. 2026-08-27 14:24 UTCEPSS rescore
  23. 2026-08-26 12:54 UTCEG score recompute
  24. 2026-08-25 13:48 UTCEPSS rescore
  25. 2026-08-25 12:07 UTCEG score recompute
Show 63 more
  1. 2026-08-24 11:19 UTCEG score recompute
  2. 2026-08-23 10:32 UTCEG score recompute
  3. 2026-08-23 00:19 UTCEPSS rescore
  4. 2026-08-22 09:45 UTCEG score recompute
  5. 2026-08-21 23:48 UTCEPSS rescore
  6. 2026-08-21 08:58 UTCEG score recompute
  7. 2026-08-20 22:55 UTCEPSS rescore
  8. 2026-08-20 08:11 UTCEG score recompute
  9. 2026-08-19 17:03 UTCEPSS rescore
  10. 2026-08-19 07:25 UTCEG score recompute
  11. 2026-08-18 13:48 UTCEPSS rescore
  12. 2026-08-18 06:38 UTCEG score recompute
  13. 2026-08-17 05:50 UTCEG score recompute
  14. 2026-08-16 14:56 UTCEPSS rescore
  15. 2026-08-16 04:45 UTCEG score recompute
  16. 2026-08-16 02:14 UTCEPSS rescore
  17. 2026-08-15 03:59 UTCEG score recompute
  18. 2026-08-15 01:30 UTCEPSS rescore
  19. 2026-08-14 03:11 UTCEG score recompute
  20. 2026-08-13 22:00 UTCEPSS rescore
  21. 2026-08-13 02:25 UTCEG score recompute
  22. 2026-08-12 13:50 UTCEPSS rescore
  23. 2026-08-12 01:38 UTCEG score recompute
  24. 2026-08-11 13:42 UTCEPSS rescore
  25. 2026-08-11 00:52 UTCEG score recompute
  26. 2026-08-10 23:59 UTCEPSS rescore
  27. 2026-08-10 00:05 UTCEG score recompute
  28. 2026-08-09 13:46 UTCEPSS rescore
  29. 2026-08-08 23:19 UTCEG score recompute
  30. 2026-08-08 16:37 UTCEPSS rescore
  31. 2026-08-07 22:32 UTCEG score recompute
  32. 2026-08-06 21:45 UTCEG score recompute
  33. 2026-08-06 13:46 UTCEPSS rescore
  34. 2026-08-05 20:58 UTCEG score recompute
  35. 2026-08-05 19:17 UTCEPSS rescore
  36. 2026-08-04 20:12 UTCEG score recompute
  37. 2026-08-04 15:09 UTCEPSS rescore
  38. 2026-08-04 10:38 UTCEPSS rescore
  39. 2026-08-03 19:25 UTCEG score recompute
  40. 2026-08-03 10:35 UTCEPSS rescore
  41. 2026-08-02 18:39 UTCEG score recompute
  42. 2026-08-02 02:26 UTCEPSS rescore
  43. 2026-08-01 17:52 UTCEG score recompute
  44. 2026-08-01 04:15 UTCEPSS rescore
  45. 2026-07-31 17:06 UTCEG score recompute
  46. 2026-07-30 16:27 UTCEPSS rescore
  47. 2026-07-30 16:10 UTCEG score recompute 2.20
  48. 2026-07-30 16:09 UTCNVD updateCVSS v3 → 5.5 · severity → MEDIUM
  49. 2026-07-30 01:30 UTCEPSS rescore
  50. 2026-07-29 13:12 UTCEG score recompute
  51. 2026-07-28 15:36 UTCEPSS rescore
  52. 2026-07-27 14:13 UTCEPSS rescore
  53. 2026-07-26 14:54 UTCEPSS rescore
  54. 2026-07-26 14:54 UTCEPSS rescore
  55. 2026-07-26 09:57 UTCEG score recompute
  56. 2026-07-25 14:17 UTCEPSS rescore
  57. 2026-07-24 14:17 UTCEPSS rescore
  58. 2026-07-23 14:18 UTCEPSS rescore
  59. 2026-07-23 03:04 UTCEG score recompute
  60. 2026-07-22 22:55 UTCEG score recompute
  61. 2026-07-22 14:08 UTCEPSS rescore
  62. 2026-07-21 23:09 UTCEG score recompute
  63. 2026-07-21 21:38 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-10679?
CVE-2026-10679 is a medium vulnerability published on July 21, 2026. The DesignWare SPI driver (drivers/spi/spidw.c) computed the SPI BAUDR clock divider as info->clockfrequency / config->frequency without validating config->frequency. spitransceive is a Zephyr syscall and its verify handler (drivers/spi/spihandlers.c) copies the caller-supplied spiconfig from…
When was CVE-2026-10679 disclosed?
CVE-2026-10679 was first published in the National Vulnerability Database on July 21, 2026, with the most recent update on July 30, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-10679 actively exploited?
CVE-2026-10679 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 97.0% of all scored CVEs.
What is the CVSS score of CVE-2026-10679?
CVE-2026-10679 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-10679?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-10679, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-10679

Explore →

Is Your Infrastructure Affected by CVE-2026-10679?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.