CVE-2026-74668 json
packet: use consistent hard_header_len in TX_RING send path
published 2026-08-22 2 mo ago modified 2026-10-16 23 d ago also EUVD-2026-64355
- cvss
- 7.8
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.1%
- EPSS 0.1% chance of exploitation in 30 days, percentile 2%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- Linux Linux 5.10.267, 5.15.218, 6.1.185, 6.6.152, 6.12.104, 6.18.45, 7.1.9, 7.2
- linux Debian 12 6.1.187-1
- linux Debian 13 6.12.105-1
- linux Debian 14 7.1.9-1
- linux-6.12 Debian 12 6.12.107-1~deb12u1
debian advisories DEBIAN-CVE-2026-74668
- linux Ubuntu 22.04 LTS 5.15.0-202.212
- linux Ubuntu 26.04 LTS 7.0.0-42.42
- linux-aws Ubuntu 22.04 LTS 5.15.0-1119.126
- linux-aws Ubuntu 26.04 LTS 7.0.0-1016.17
- linux-gcp Ubuntu 22.04 LTS 5.15.0-1120.130
- linux-gcp Ubuntu 26.04 LTS 7.0.0-1016.18
- linux-gke Ubuntu 22.04 LTS 5.15.0-1115.121
- linux-ibm Ubuntu 22.04 LTS 5.15.0-1113.117
ubuntu advisories UBUNTU-CVE-2026-74668
Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
- git.kernel.org/stable/c/9c7e8ff48c377bef18c3d178748aea0575b69ede commit
- git.kernel.org/stable/c/2a73b2c37ee3060a880b53cd24783d93fc7be5f8 commit
- git.kernel.org/stable/c/e79f59a8527a49078cfaf8fe8fb5fcefc20c76d2 commit
- git.kernel.org/stable/c/d85d2fd54e901637c81d847811e03c662aee13cd commit
- git.kernel.org/stable/c/016763e829cac37b3234eace86fd0a4c560de4a7 commit
- git.kernel.org/stable/c/27e068d1b35dbec10a3cf268887c94407be4badc commit
- git.kernel.org/stable/c/d48ea5c9c4c34dc0df621f0e39ed3a16b644621a commit
- git.kernel.org/stable/c/21b5953e7494c16a42e6cd8cf110e18d13ae4a6b commit
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2026-74668 updated cvss 5.5
kernel: packet: use consistent hard_header_len in TX_RING send path
-
Red Hat Enterprise Linux 6 perf, kernel, python-perf, kernel-kdump, kernel-firmware, kernel-bootwrapper, +1 moreaffected: workaround, no fix planned “Out of support scope”
-
Red Hat Enterprise Linux 7 perf, kernel, bpftool, kernel-rt, python-perf, kernel-kdump, +8 more Red Hat Enterprise Linux 8 perf, kernel, bpftool, kernel-rt, kernel-core, kernel-tools, +29 more Red Hat Enterprise Linux 9 rv, perf, rtla, kernel, bpftool, libperf, +83 more Red Hat Enterprise Linux 10 kernelaffected: workaround, no fix available “Fix deferred”
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
- Assessed
- 23 d ago
Exploit prediction
0.13% chance of exploitation in the next 30 days, higher than 2% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 7.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
Affected products
- Linux Linux
Classification
- Technology feeds
References
- git.kernel.org /stable/c/9c7e8ff48c377bef18c3d178748aea0575b69ede
- git.kernel.org /stable/c/2a73b2c37ee3060a880b53cd24783d93fc7be5f8
- git.kernel.org /stable/c/e79f59a8527a49078cfaf8fe8fb5fcefc20c76d2
- git.kernel.org /stable/c/d85d2fd54e901637c81d847811e03c662aee13cd
- git.kernel.org /stable/c/016763e829cac37b3234eace86fd0a4c560de4a7
- git.kernel.org /stable/c/27e068d1b35dbec10a3cf268887c94407be4badc
- git.kernel.org /stable/c/d48ea5c9c4c34dc0df621f0e39ed3a16b644621a
- git.kernel.org /stable/c/21b5953e7494c16a42e6cd8cf110e18d13ae4a6b
Sources
- CVE List CVE-2026-74668
- NVD CVE-2026-74668
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.