CVE-2026-10683

mediumpriority · track · 18EPSS 0.002 · 15 %ileEUUS
grimoire priorityP3 · Track
Exploitable?
—
no known exploitation
Likely / severe?
0.24% (15th) EPSS
CVSS 4.6 · medium
Is it mine?
2 products
Check your exposure
Who says so?
2 sources
enisa_euvd · nvd

EPSS · scored 2026-10-27

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.

01

cvss

Technical severity, 0–10. One row per scoring source.

4.6
010

base score 0–10 · higher = more severe · hover a vector to decode⚠ sources disagree · low–medium · 2.4–4.6

v3.14.6mediumCVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:Hprimary · NVD / NIST USexploitability 0.9 · impact 3.6
v3.12.4lowCVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:Lsecondary · ENISA EU
v3.12.4lowCVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:Lsecondary · vulnerabilities@zephyrproject.orgexploitability 0.9 · impact 1.4
v3.14.2mediumCVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H/E:Usecondary · CVSS-BT (t0sche)
02

ssvc

A stakeholder decision — act, attend, or track — from exploitation and impact.

Trackcoordinatorcisa_ssvcUS
03

weaknesses

The CWE weakness classes this flaw belongs to.

04

affected products (2)

Products and version ranges known to be affected.

05

also known as (1)

Other names and identifiers for this entity.

06

sources

Which sources assert this record, and when.

published 2026-07-27modified 2026-10-24
07

references (4)

External citations — patches, advisories, analysis.

scry

Attackers weaponise vulnerabilities like this against internet-exposed services. See what is exposed on your perimeter with a free passive scan.

Free scan