CVE-2026-95826: Out-of-bounds write in the SMSC911x Ethernet driver when transmitting frames larger than the staging buffer

Published Nov 20, 2026
·
Updated

The SMSC911x/LAN9220 Ethernet driver stages every outgoing frame in a fixed-size static buffer before pushing it to the controller FIFO. ethtx() in drivers/ethernet/ethsmsc911x.c took the frame length from netpktgetlen(pkt) and passed it directly to netpktread(pkt, txbuf, totallen), with no comparison against the size of txbuf (NETETHMAXFRAMESIZE). netpktread() 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: ethernetsend() 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 CONFIGNETIPV6FRAGMENT 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: handlerainput() in subsys/net/ip/ipv6nbr.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 txbuf, 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 NETETHMAXFRAMESIZE with -EMSGSIZE before any TXDATAPORT write, so the controller FIFO is also not left holding a command word without its payload.

Affected Software

1 affected component
Zephyr Project Zephyr

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Compensating control

    In the SMSC911x/LAN9220 transmit path, reject frames larger than NET_ETH_MAX_FRAME_SIZE with -EMSGSIZE before writing to TX_DATA_PORT.

Event History

Nov 20, 2026
CVE Published
via MITRE·05:54 PM
Data Sourced
via MITRE·05:54 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·06:18 PM
DescriptionSeverityWeakness

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203