CVE-2026-80742

af_packet: Don't send zero-byte data in tpacket_snd().

N/A
Published: September 3, 2026 at 08:26 AM UTC
Updated: September 3, 2026 at 01:34 PM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

Description

In the Linux kernel, the following vulnerability has been resolved: af_packet: Don't send zero-byte data in tpacket_snd(). syzbot reported a WARNING in __dev_queue_xmit() triggered via tpacket_snd(): skb_assert_len WARNING: at include/linux/skbuff.h:2753 skb_assert_len WARNING: at __dev_queue_xmit+0x21bc/0x4970 net/core/dev.c:4781 Call Trace: <TASK> dev_queue_xmit include/linux/netdevice.h:3448 [inline] packet_xmit+0x243/0x310 net/packet/af_packet.c:276 tpacket_snd net/packet/af_packet.c:2907 [inline] packet_sendmsg+0x28d6/0x4eb0 net/packet/af_packet.c:3134 When sending 0-byte packets via TPACKET ring buffer on devices with no hard header (e.g. dev->hard_header_len == 0), tpacket_fill_skb() populates an skb with skb->len == 0 and returns 0. tpacket_snd() then forwards this empty skb to packet_xmit(), causing __dev_queue_xmit() to hit skb_assert_len(skb). Similar checks exist in packet_snd() via commit dc633700f00f ("net/af_packet: check len when min_header_len equals to 0") and in packet_sendmsg_spkt() via commit 6a341729fb31 ("af_packet: Don't send zero-byte data in packet_sendmsg_spkt()."). Return -EINVAL in tpacket_fill_skb() when skb->len is zero to reject zero-length packets in tpacket_snd().

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

2.6.12 ≤ v < 5.10.2662.6.12 ≤ v < 5.15.2172.6.12 ≤ v < 6.1.1842.6.12 ≤ v < 6.12.1052.6.12 ≤ v < 6.18.462.6.12 ≤ v < 6.6.1532.6.12 ≤ v < 7.1.102.6.12 ≤ v < 7.21da177e4c3f41524e886b7f1b8a0c1fc7321cac22.6.12
Vendor states this is fixed in 1fc70b3d513bafb16b17540178870ef46e81c0bb (fixed)
Vendor states this is fixed in 3fa110f9e2ea96f567f2194c673c4bc327640111 (fixed)
Vendor states this is fixed in 6bcd76c134c55c697148acb5c0194e9666abdf84 (fixed)
Vendor states this is fixed in 7521e691c7c4f2231634c95053281ac888d1f452 (fixed)
Vendor states this is fixed in 80a702964467b998d254f16cc61c2c9a20540c9d (fixed)
Vendor states this is fixed in 98c5914d6b7bd4b4675535908e57dea31f1efd6a (fixed)
Vendor states this is fixed in dde212f8622f5cb36223fff1ebd6e6f2a3dc61fe (fixed)
Vendor states this is fixed in f09ac5682f1bb67981fcb6ead4d3cfe439225876 (fixed)
Vendor states this is fixed in 2.6.12 (unaffected)
Vendor states this is fixed in 5.10.266 (unaffected)
Vendor states this is fixed in 5.15.217 (unaffected)
Vendor states this is fixed in 6.1.184 (unaffected)
Vendor states this is fixed in 6.12.105 (unaffected)
Vendor states this is fixed in 6.18.46 (unaffected)
Vendor states this is fixed in 6.6.153 (unaffected)
Vendor states this is fixed in 7.1.10 (unaffected)
Vendor states this is fixed in 7.2 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card