CVE-2026-74668

packet: use consistent hard_header_len in TX_RING send path

HIGH
7.8
CVSS Score
Published: August 22, 2026 at 03:32 PM UTC
Updated: October 16, 2026 at 08:17 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
HIGH7.8
Exploit prediction
EPSS 0.1%
SSVC
No known exploit

Description

In the Linux kernel, the following vulnerability has been resolved: packet: use consistent hard_header_len in TX_RING send path tpacket_snd() reads dev->hard_header_len independently for skb allocation and header construction in tpacket_fill_skb(). Concurrent netdevice reconfiguration can therefore make the reserved headroom smaller than the amount later pushed, or make copylen - hard_header_len negative. Snapshot hard_header_len once before processing ring frames and use it for the frame limit, headroom allocation, copy length, and skb construction. Pass the snapshot to tpacket_fill_skb(). The separate SOCK_DGRAM consistency problem between hard_header_len and header_ops->create is not addressed here.

Affected

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

2.6.3169e3c75f4d541a6eb151b3ef91f34033cb3ad6e1
Vendor states this is fixed in 016763e829cac37b3234eace86fd0a4c560de4a7 (fixed)
Vendor states this is fixed in 21b5953e7494c16a42e6cd8cf110e18d13ae4a6b (fixed)
Vendor states this is fixed in 27e068d1b35dbec10a3cf268887c94407be4badc (fixed)
Vendor states this is fixed in 2a73b2c37ee3060a880b53cd24783d93fc7be5f8 (fixed)
Vendor states this is fixed in 9c7e8ff48c377bef18c3d178748aea0575b69ede (fixed)
Vendor states this is fixed in d48ea5c9c4c34dc0df621f0e39ed3a16b644621a (fixed)
Vendor states this is fixed in d85d2fd54e901637c81d847811e03c662aee13cd (fixed)
Vendor states this is fixed in e79f59a8527a49078cfaf8fe8fb5fcefc20c76d2 (fixed)
Vendor states this is fixed in 2.6.31 (unaffected)
Vendor states this is fixed in 5.10.267 (unaffected)
Vendor states this is fixed in 5.15.218 (unaffected)
Vendor states this is fixed in 6.1.185 (unaffected)
Vendor states this is fixed in 6.12.104 (unaffected)
Vendor states this is fixed in 6.18.45 (unaffected)
Vendor states this is fixed in 6.6.152 (unaffected)
Vendor states this is fixed in 7.1.9 (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.

SSVC — Action Prioritization

SSVCNo known exploitNot automatableTotal impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

7.8HIGHLinux
Vector?

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