CVE-2026-80742af_packet: Don't send zero-byte data in tpacket_snd().
Updated under an hour ago ()
Does this affect you?
It affects Linux. Add what you run to find out whether that includes you.
No exploitation reported and no EPSS estimate yet.
Do this next
Free account, 1 product
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().
- CVSS
- Not yet scored
- Weakness (CWE)
- Not given
- Known exploited
- Not in CISA's KEV catalog
- EPSS (exploitation in the next 30 days)
- Not loaded for this CVE
- Assigned by
- Linux
- NVD analysis
- Received
- Record last updated
- Sep 3, 2026
- First seen by InfoSec Signals
- Oct 9, 2026
Affected products
Linux Linux linux:linux (from the name) | from 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 before dde212f8622f5cb36223fff1ebd6e6f2a3dc61fe; from 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 before 80a702964467b998d254f16cc61c2c9a20540c9d; from 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 before 7521e691c7c4f2231634c95053281ac888d1f452; from 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 before 1fc70b3d513bafb16b17540178870ef46e81c0bb; from 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 before 3fa110f9e2ea96f567f2194c673c4bc327640111; from 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 before 98c5914d6b7bd4b4675535908e57dea31f1efd6a; from 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 before f09ac5682f1bb67981fcb6ead4d3cfe439225876; from 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 before 6bcd76c134c55c697148acb5c0194e9666abdf84 | CNA record |
References
- https://git.kernel.org/stable/c/dde212f8622f5cb36223fff1ebd6e6f2a3dc61fe
- https://git.kernel.org/stable/c/80a702964467b998d254f16cc61c2c9a20540c9d
- https://git.kernel.org/stable/c/7521e691c7c4f2231634c95053281ac888d1f452
- https://git.kernel.org/stable/c/1fc70b3d513bafb16b17540178870ef46e81c0bb
- https://git.kernel.org/stable/c/3fa110f9e2ea96f567f2194c673c4bc327640111
- https://git.kernel.org/stable/c/98c5914d6b7bd4b4675535908e57dea31f1efd6a
- https://git.kernel.org/stable/c/f09ac5682f1bb67981fcb6ead4d3cfe439225876
- https://git.kernel.org/stable/c/6bcd76c134c55c697148acb5c0194e9666abdf84
The CVE record on cve.org NVD's entry
The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.