# CVE-2026-93670 — zephyrproject zephyr

> As of 2026-11-17, CVE-2026-93670 is a LOW-severity vulnerability in zephyrproject zephyr, CVSS v3.1 3.5, EPSS 0.1% (3.4th percentile). No Threadlinqs-tracked threat campaign has been attributed to CVE-2026-93670 as of 2026-11-17; the identifier is re-checked against the Threadlinqs threat corpus on every daily ingest.

**Last updated:** 2026-11-17

## What is CVE-2026-93670?

The Synopsys DesignWare I3C controller driver (drivers/i3c/i3c_dw.c) tracks free Device Address Table (DAT) slots with get_free_pos(), which signals an exhausted table by returning -1. The helper declared its return type as uint8_t, so the sentinel was truncated to 255, and both consumers (dw_i3c_attach_device() and dw_i3c_i2c_attach_device()) also stored it in a uint8_t before testing if (pos dw_i3c_i2c_priv_data[255].id, more than 200 bytes past the end of the 32-element dw_i3c_i2c_priv_data array and past the end of struct dw_i3c_data; it stores the resulting out-of-bounds address in desc->controller_priv, from which later detach, reattach and IBI operations read the slot index back; and it performs a 32-bit MMIO store 1020 bytes beyond the hardware DAT base, outside the table the controller reports. The attach still returns success, so the upper layer believes the device is bound. The DAT is smaller than the software array (its depth is read from DEVICE_ADDR_TABLE_POINTER, commonly 8 or 16 entries), so exhaustion is reachable. In a dual-role build (CONFIG_I3C_DUAL_ROLE with CONFIG_I3C_USE_IBI) acting as a secondary controller, the attach count is supplied by the bus's active controller: i3c_sec_handoffed() attaches one device per entry of the received DEFTGTS list, so a hostile or malfunctioning controller on the local I3C bus that declares more targets than the local DAT depth triggers the condition once per surplus entry. Exhaustion can also be reached from a devicetree that declares more devices than the table holds, or by repeated i3c attach shell commands. Impact is bounded: the out-of-bounds store is a single byte of fixed value at a fixed displacement, with no attacker-chosen data or offset, so the realistic outcomes are corruption of neighbouring static driver state, writes into reserved controller registers, and inconsistent driver bookkeeping (a crash or a wedged I3C bus) rather than a controllable memory-write primitive. The attack vector is the local chip-to-chip I3C bus; there is no network-reachable path.

The record classifies CVE-2026-93670 under weakness class [CWE-787](https://intel.threadlinqs.com/cwe/CWE-787). Its CVSS v3 base vector states that the flaw requires physical access to the device, needs no prior authentication, needs no user interaction. 1 affected-product entry is recorded, across 1 vendor, listed below. The identifier was first published 3 days ago.

## Severity and exploitation probability

- **CVSS v3.1 base score:** 3.5 — LOW (`CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L`)
- **EPSS (FIRST):** 0.1% probability of exploitation in the next 30 days, higher than 3.4% of all scored CVEs
- **CISA KEV:** Not listed in the CISA Known Exploited Vulnerabilities catalog
- **Threadlinqs priority:** 1.9/10 — a Threadlinqs composite of the CVSS base score, the EPSS percentile and public exploit availability
- **Published:** 2026-11-16

## Is CVE-2026-93670 being exploited?

It currently carries a trending score of 31 in the Threadlinqs vulnerability feed.

## Affected products and versions

- [zephyrproject](https://intel.threadlinqs.com/vendors/zephyrproject): zephyr

## How to fix CVE-2026-93670

Patch reference: [https://github.com/zephyrproject-rtos/zephyr/commit/1df24c85842da26b24c14b7cfcd51928a86b5530](https://github.com/zephyrproject-rtos/zephyr/commit/1df24c85842da26b24c14b7cfcd51928a86b5530). Apply the vendor fix referenced above to every affected product listed in this record, then confirm the running version against the vendor advisory.

## Threat activity tracking CVE-2026-93670

No threat campaign in the Threadlinqs corpus currently references CVE-2026-93670, in its CVE list or as an indicator. The linkage is recomputed from the live corpus on every daily ingest, so this section fills in as soon as a tracked campaign cites the identifier.

## Sources

Enriched from CVE.org, NVD, FIRST EPSS. This product uses the NVD API but is not endorsed or certified by the NVD.

**Vendor advisory and patch**

- [github.com — patch](https://github.com/zephyrproject-rtos/zephyr/commit/1df24c85842da26b24c14b7cfcd51928a86b5530)

**Other references**

- [github.com](https://github.com/zephyrproject-rtos/zephyr/security/advisories/GHSA-5jhj-95j8-x5gf)

Canonical: https://intel.threadlinqs.com/cve/CVE-2026-93670
No Threadlinqs detection currently covers CVE-2026-93670; it is re-checked on every ingest.
Indicator values unlock with TL Creds (https://threadlinqs.com/tl-creds); MCP access for AI agents needs Purple: https://intel.threadlinqs.com/mcp
