CVE-2026-10683
LOWDescription
In the Synopsys DesignWare I2C driver (drivers/i2c/i2c_dw.c) operating in target/slave mode, the rx_full interrupt handler gates the write_requested() callback on dw->state != CMD_SEND, and dw->state is only reset to READY on a STOP interrupt. The START_DET interrupt, whose handler in i2c_dw_slave_read_clear_intr_bits() would reset the state on every (re)START, was never added to the enabled interrupt mask in i2c_dw_slave_register(), so that recovery path was dead code. As a result, if the STOP interrupt is lost (bus glitch/reset, or a concurrent master driving STOP) or the bus master issues a legal WRITE-repeated-START-WRITE sequence with the same direction, the driver remains in CMD_SEND permanently and never invokes write_requested() again for the life of the target. An I2C master on the same physical bus can deliberately trigger this, causing the I2C target function to malfunction for all subsequent write transactions and desynchronizing consumer framing state (e.g. MCTP-over-I2C), a recoverable-by-reset denial of service of the target peripheral. The fix unmasks START_DET so the state is reset at every bus (re)START. Impact is availability-only over a local board-level bus; no memory corruption results in the in-tree consumer, whose per-byte buffer write is independently bounds-checked.
How to fix
TridentStack Control can deploy fixes like this automatically across your Windows, macOS, and Linux fleet. See how it works
Remediation is compiled from vendor and distribution security advisories. Always confirm against the linked source for your exact version and platform.
CVSS v3 Vector
Exploitability
Impact
CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
Exploit Intelligence
Low risk: more likely to be exploited than 6% of all known CVEs.
References
Related Vulnerabilities
Other CWE-835 vulnerabilities, ordered by exploit likelihood. View all
| CVE | Severity | CVSS | EPSS | Exploited | Fix |
|---|---|---|---|---|---|
| CVE-2020-13935 | High | 7.5 | 87% | - | Fix |
| CVE-2020-36227 | High | 7.5 | 78% | - | Fix |
| CVE-2022-0778 | High | 7.5 | 73% | - | Fix |
| CVE-2024-20353 | High | 8.6 | 71% | KEV | - |
| CVE-2023-34966 | High | 7.5 | 62% | - | Fix |
| CVE-2019-14241 | High | 7.5 | 61% | - | - |
Common questions
How do I fix CVE-2026-10683?
Upgrade zephyr to 4.5.0 or later.
Is CVE-2026-10683 being actively exploited?
Not that we know of. CVE-2026-10683 is not in the CISA Known Exploited Vulnerabilities catalog. Its EPSS score of 0.16% is the estimated probability that it will be exploited in the next 30 days. That is higher than 6% of all scored CVEs.
How severe is CVE-2026-10683?
CVE-2026-10683 has a CVSS v3 base score of 2.4, rated low. CVSS rates the technical impact if the vulnerability is exploited, not how likely that is, so weigh it alongside the exploit-prediction score when you decide what to patch first.
What does CVE-2026-10683 affect?
Published advisories record a fix for zephyr (NVD). Only products with a sourced advisory are listed, so treat this as what we can cite rather than a complete inventory.
Embed a live status badge for CVE-2026-10683
Markdown
[](https://tridentstack.com/cve/CVE-2026-10683)HTML
<a href="https://tridentstack.com/cve/CVE-2026-10683"><img src="https://tridentstack.com/cve/badge/CVE-2026-10683.svg" alt="CVE-2026-10683"></a>Find and fix vulnerabilities across your fleet
TridentStack Control continuously scans your Windows, macOS, and Linux fleet for known vulnerabilities, prioritizes them by severity and active exploitation, and patches them automatically.
This product uses NVD data but is not endorsed or certified by the NVD. EPSS scores courtesy of FIRST.org (https://www.first.org/epss). Source: CISA KEV Catalog. Data as of 2026-08-12.