CVE-2026-74668packet: use consistent hard_header_len in TX_RING send path
- 7.8HighCVSS base score
- 0.13%Exploitation in 30 daysEPSS · top 97% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
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.
Timeline
ID reserved
By Linux
- 7 days later
· 7 days later
Published
- 55 days later
· 55 days later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| LinuxCNA (assigner) | 3.1 | High7.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
| NVDNVD · Received | 3.1 | High7.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
- EPSS (exploitation in 30 days)
- 0.13% · top 97% of all CVEs (15 Nov 2026)
- CISA SSVC
- Exploitation: none · Automatable: no · Technical impact: total
The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.8.
Affected products
- affected 69e3c75f4d541a6eb151b3ef91f34033cb3ad6e1 – < 9c7e8ff48c377bef18c3d178748aea0575b69ede
- affected 69e3c75f4d541a6eb151b3ef91f34033cb3ad6e1 – < 2a73b2c37ee3060a880b53cd24783d93fc7be5f8
- affected 69e3c75f4d541a6eb151b3ef91f34033cb3ad6e1 – < e79f59a8527a49078cfaf8fe8fb5fcefc20c76d2
- affected 69e3c75f4d541a6eb151b3ef91f34033cb3ad6e1 – < d85d2fd54e901637c81d847811e03c662aee13cd
- affected 69e3c75f4d541a6eb151b3ef91f34033cb3ad6e1 – < 016763e829cac37b3234eace86fd0a4c560de4a7
- affected 69e3c75f4d541a6eb151b3ef91f34033cb3ad6e1 – < 27e068d1b35dbec10a3cf268887c94407be4badc
- affected 69e3c75f4d541a6eb151b3ef91f34033cb3ad6e1 – < d48ea5c9c4c34dc0df621f0e39ed3a16b644621a
- affected 69e3c75f4d541a6eb151b3ef91f34033cb3ad6e1 – < 21b5953e7494c16a42e6cd8cf110e18d13ae4a6b
- affected 2.6.31
- unaffected < 2.6.31
- unaffected 5.10.267 – ≤ 5.10.*
- unaffected 5.15.218 – ≤ 5.15.*
- unaffected 6.1.185 – ≤ 6.1.*
- unaffected 6.6.152 – ≤ 6.6.*
- unaffected 6.12.104 – ≤ 6.12.*
- unaffected 6.18.45 – ≤ 6.18.*
- unaffected 7.1.9 – ≤ 7.1.*
- unaffected 7.2 – ≤ *
References
References8
- https://git.kernel.org/stable/c/9c7e8ff48c377bef18c3d178748aea0575b69ede (opens in a new tab)
- https://git.kernel.org/stable/c/2a73b2c37ee3060a880b53cd24783d93fc7be5f8 (opens in a new tab)
- https://git.kernel.org/stable/c/e79f59a8527a49078cfaf8fe8fb5fcefc20c76d2 (opens in a new tab)
- https://git.kernel.org/stable/c/d85d2fd54e901637c81d847811e03c662aee13cd (opens in a new tab)
- https://git.kernel.org/stable/c/016763e829cac37b3234eace86fd0a4c560de4a7 (opens in a new tab)
- https://git.kernel.org/stable/c/27e068d1b35dbec10a3cf268887c94407be4badc (opens in a new tab)
- https://git.kernel.org/stable/c/d48ea5c9c4c34dc0df621f0e39ed3a16b644621a (opens in a new tab)
- https://git.kernel.org/stable/c/21b5953e7494c16a42e6cd8cf110e18d13ae4a6b (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-64355 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-74668)Record last updated .