Linux Kernel up to 7.1.9 af_packet net/packet/af_packet.c tpacket_snd input validation

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
4.7$0-$5k0.94+

Summaryinfo

A vulnerability has been found in Linux Kernel up to 7.1.9 and classified as problematic. This affects the function tpacket_snd of the file net/packet/af_packet.c of the component af_packet. The manipulation leads to input validation. This vulnerability is referenced as CVE-2026-80742. Remote exploitation of the attack is possible. No exploit is available.

Detailsinfo

A vulnerability was found in Linux Kernel up to 7.1.9 and classified as problematic. This issue affects the function tpacket_snd of the file net/packet/af_packet.c of the component af_packet. The manipulation with an unknown input leads to a input validation vulnerability. Using CWE to declare the problem leads to CWE-20. The product receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required to process the data safely and correctly. Impacted is availability. The summary by CVE is:

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

The advisory is shared at git.kernel.org. The identification of this vulnerability is CVE-2026-80742 since 08/26/2026. The exploitation is known to be easy. The attack may be initiated remotely. The exploitation requires an enhanced level of successful authentication. Technical details are known, but no exploit is available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 09/03/2026).

Upgrading to version 5.10.266, 5.15.217, 6.1.184, 6.6.153, 6.12.105, 6.18.46 or 7.1.10 eliminates this vulnerability. Applying the patch dde212f8622f5cb36223fff1ebd6e6f2a3dc61fe/80a702964467b998d254f16cc61c2c9a20540c9d/7521e691c7c4f2231634c95053281ac888d1f452/1fc70b3d513bafb16b17540178870ef46e81c0bb/3fa110f9e2ea96f567f2194c673c4bc327640111/98c5914d6b7bd4b4675535908e57dea31f1efd6a/f09ac5682f1bb67981fcb6ead4d3cfe439225876/6bcd76c134c55c697148acb5c0194e9666abdf84 is able to eliminate this problem.

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Type

Vendor

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 4.9
VulDB Meta Temp Score: 4.7

VulDB Base Score: 4.9
VulDB Temp Score: 4.7
VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍

Exploitinginfo

Class: Input validation
CWE: CWE-20
CAPEC: 🔒
ATT&CK: 🔒

Physical: No
Local: No
Remote: Yes

Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔒

Upgrade: Kernel 5.10.266/5.15.217/6.1.184/6.6.153/6.12.105/6.18.46/7.1.10
Patch: dde212f8622f5cb36223fff1ebd6e6f2a3dc61fe/80a702964467b998d254f16cc61c2c9a20540c9d/7521e691c7c4f2231634c95053281ac888d1f452/1fc70b3d513bafb16b17540178870ef46e81c0bb/3fa110f9e2ea96f567f2194c673c4bc327640111/98c5914d6b7bd4b4675535908e57dea31f1efd6a/f09ac5682f1bb67981fcb6ead4d3cfe439225876/6bcd76c134c55c697148acb5c0194e9666abdf84

Timelineinfo

08/26/2026 CVE reserved
09/03/2026 +8 days Advisory disclosed
09/03/2026 +0 days VulDB entry created
09/03/2026 +0 days VulDB entry last update

Sourcesinfo

Vendor: kernel.org

Advisory: git.kernel.org
Status: Confirmed

CVE: CVE-2026-80742 (🔒)
GCVE (CVE): GCVE-0-2026-80742
GCVE (VulDB): GCVE-100-398345

Entryinfo

Created: 09/03/2026 10:57
Changes: 09/03/2026 10:57 (60)
Complete: 🔍
Cache ID: 216::103

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

Interested in the pricing of exploits?

See the underground prices here!