CVE-2026-10683 Details
Description
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.
A denial-of-service vulnerability has been identified in the Synopsys DesignWare I2C driver, specifically in versions 4.0.0 through 4.4.1, when operating in target/slave mode. The issue arises because the 'rx_full' interrupt handler prevents the 'write_requested()' callback from being called if the driver's state is not 'CMD_SEND'. The state is only reset to 'READY' upon receiving a STOP interrupt. If this STOP interrupt is missed—due to a bus glitch, reset, or another master driving the STOP—or if the master sends a legal WRITE-repeated-START-WRITE sequence, the driver remains stuck in 'CMD_SEND' and fails to invoke 'write_requested()' for the duration of the target's life. This malfunction can disrupt I2C target functions and desynchronize consumer framing states, such as with MCTP-over-I2C, leading to a local, recoverable-by-reset denial-of-service on the target peripheral.
Users can upgrade to Zephyr version 4.5.0, where this vulnerability has been patched. The fix has been merged into the main branch and is also available in the v4.4-branch and v4.3-branch.
Metrics
CVSS 4.0 Severity and Vector Strings:
No CVSS 4.0 data is available for this CVE.
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
CISA-ADP
Assessed Jul 27, 2026References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| CWE-835 | Loop with Unreachable Exit Condition ('Infinite Loop') | [email protected] |
Affected Products
| Product | Versions |
|---|---|
| zephyrproject zephyr | >= 4.0.0, < 4.5.0 |
CPE
Remediation
| |
Change History
6 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Nov 4, 2026 | CVE Modified | [email protected] |
| Oct 24, 2026 | CVE Translated | [email protected] |
| Sep 1, 2026 | CVE Modified | [email protected] |
| Aug 12, 2026 | Initial Analysis | [email protected] |
| Jul 27, 2026 | New CVE Received | [email protected] |
| Jul 27, 2026 | CVE Modified | CISA-ADP |