CVE-2026-95826 — CWE-787
CVE-2026-95826 is a HIGH severity Memory Corruption / Buffer Overflow vulnerability (CWE-787) (CVSS 7.5/10) affecting affected software system. Technical vector analysis shows that an attacker can exploit this flaw via adjacent network (AV:A) without authentication (PR:N) with zero user interaction (UI:N), resulting in complete compromise of system confidentiality and integrity (C:H/I:H).
📄 Official NVD / MITRE Original Record Text
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.
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
CVE-2026-95826
CVSS 7.5/10 · HIGH · 20.11.2026
CWE: CWE-787
Vector: CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
🎯 WHAT IS THIS VULNERABILITY?
Buffer Overflow / Memory Corruption
Summary: 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 destinat…
⚡ ATTACK CHAIN
1. Fuzz with Boofuzz/AFL++ to find crash.
2. Find offset: pattern_create→crash→pattern_offset EIP
3. Control EIP/RIP, bypass NX with ROP chains.
4. ASLR bypass via info leak or brute force.
5. Metasploit: search CVE-XXXX; use exploit/...; run
🔧 Tools: GDB+PEDA/pwndbg, ROPgadget, pwntools, Metasploit, AFL++
🗺️ MITRE ATT&CK: T1203 (Exploitation for Client Execution), T1068
🌍 REAL WORLD IMPACT
All confidential data readable/stealable; data can be modified or deleted; service can be completely taken down.
🛡️ REMEDIATION
→ Apply the vendor-released patch immediately.
→ Verify ASLR/NX/Stack Canary are active.
→ Add WAF rule, create IDS alert for anomalous traffic.
⚠️ URGENCY
⚠️ Planned maintenance (2 weeks).
────────────────────────────────────────
[Kural Tabanlı Otomatik Güvenlik Analizi]