# CVE-2026-10673: Out-of-bounds write in ADIN2111/ADIN1110 OA SPI Ethernet RX frame reassembly

> An attacker on the Ethernet segment can trigger an out-of-bounds write in the ADIN2111/ADIN1110 driver, potentially causing code execution or denial of service.

- **Severity:** High 8.3 (`CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Jul 2026
- **Updated:** 15 Oct 2026
- **Also known as:** GHSA-hm6v-4jh4-3qc4

## What is CVE-2026-10673?

CVE-2026-10673 is a high-severity memory corruption vulnerability in Zephyrproject Zephyr, published on 15 Jul 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The Zephyr ADIN2111/ADIN1110 10BASE-T1S/T1L Ethernet driver (drivers/ethernet/eth_adin2111.c) reassembles received Ethernet frames in OPEN Alliance (OA) SPI mode by copying device-supplied 64-byte data chunks into a fixed static buffer ctx->buf of size CONFIG_ETH_ADIN2111_BUFFER_SIZE (default 1524 bytes). In eth_adin2111_oa_data_read(), each valid chunk was memcpy'd into ctx->buf[ctx->scur] and the write cursor scur advanced, with no check that scur + len stayed within the buffer. The number of chunks (up to 255, from the BUFSTS RCA field) and the per-chunk length are taken entirely from the frame data received off the wire; the cursor is only reset on a start-of-frame chunk. An attacker on the single-pair Ethernet segment can therefore send a frame whose reassembled size exceeds the configured buffer, causing the driver's RX offload thread to write attacker-controlled frame bytes past the end of the static buffer into adjacent driver/kernel memory (up to roughly 14.8 KB in the worst case). This is a remotely/adjacently reachable out-of-bounds write (CWE-787) that can corrupt memory and cause denial of service or potentially code execution. The defect was introduced when OA SPI support was added (commit 0ca8b0756b1) and shipped in releases v3.7.0 through v4.4.0. The fix adds a bounds check that drops the oversized frame and resets the cursor before the copy.

Weakness: CWE-787 (Out-of-bounds Write), CWE-125 (Out-of-bounds Read)

## Which versions are affected by CVE-2026-10673?

It affects 1 product.


Products: Zephyrproject Zephyr.

## How do I fix CVE-2026-10673?

No fix has been published for CVE-2026-10673 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-10673 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-10673 exists.

## Other vulnerabilities in Zephyrproject Zephyr

- [CVE-2026-5067](https://insights.sbomify.com/CVE-2026-5067/): Out-of-bounds read/write in HTTP WebSocket upgrade via non-null-terminated Sec-WebSocket-Key (critical 9.8)
- [CVE-2022-3806](https://insights.sbomify.com/CVE-2022-3806/): Bluetooth HCI Error Handling Double Free (critical 9.8)
- [CVE-2017-14199](https://insights.sbomify.com/CVE-2017-14199/): Memory corruption in getaddrinfo (critical 9.8)
- [CVE-2018-1000800](https://insights.sbomify.com/CVE-2018-1000800/): Null dereference in n/a (critical 9.8)
- [CVE-2021-3329](https://insights.sbomify.com/CVE-2021-3329/): DOS: Incorrect handling of the initial HCI ACL_MTU handshake packet leads to crash of bluetooth host layer (critical 9.6)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-10673 and fix it if it is affected.

What it is: CVE-2026-10673 is a high-severity memory corruption vulnerability in Zephyrproject Zephyr, published on 15 Jul 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-10673 exists.

Affected product: Zephyrproject Zephyr. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-10673/ (Markdown: https://insights.sbomify.com/CVE-2026-10673/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-10673
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-10673
- OSV: https://osv.dev/vulnerability/CVE-2026-10673

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-10673/
Summaries are generated and may contain mistakes; the official description above is the record.