CVE-2026-80742

CVE CVE-2026-80742EUVD EUVD-2026-70346Published 2026-09-03T08:26:25.000Z

What the advisory describes

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().

Source: EUVD (ENISA), in the words of the advisory.

Products the advisory names

These come from the advisory itself, not from any check we performed.

Linux — Linux 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <98c5914d6b7bd4b4675535908e57dea31f1efd6a; patch: 6.1.184; 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <1fc70b3d513bafb16b17540178870ef46e81c0bb; 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <3fa110f9e2ea96f567f2194c673c4bc327640111; 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <dde212f8622f5cb36223fff1ebd6e6f2a3dc61fe; 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <7521e691c7c4f2231634c95053281ac888d1f452; 2.6.12; patch: 5.10.266; patch: 7.1.10; patch: 7.2; patch: 5.15.217; patch: 0; patch: 6.6.153; 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <80a702964467b998d254f16cc61c2c9a20540c9d; patch: 6.18.46; 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <6bcd76c134c55c697148acb5c0194e9666abdf84; 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <f09ac5682f1bb67981fcb6ead4d3cfe439225876; patch: 6.12.105

The versions shown are the advisory's own. Patchlage compares no version numbers and derives no judgement from them — which version is installed is something a person has to look up.

Carried in the product catalogue

An estate covering these products can be recorded in Patchlage. An advisory about them appears in the next morning's situation report.

Linux — Linux

Does this concern one of your customers?

This page cannot answer that — it does not know your estate. Whoever has recorded their environments gets the answer the morning after publication, together with a paragraph they can forward to the customer unedited.

Try it for 28 days

Patchlage reports hits and suspected hits. About everything else this system says nothing — neither this page nor the situation report ever claims that an estate is safe.