Linux
packet: use consistent hard_header_len in TX_RING send path
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 versions and mitigation
From the CVE record and the vendor's references.Affected
- >= 69e3c75f4d541a6eb151b3ef91f34033cb3ad6e1, < 9c7e8ff48c377bef18c3d178748aea0575b69ede
- >= 69e3c75f4d541a6eb151b3ef91f34033cb3ad6e1, < 2a73b2c37ee3060a880b53cd24783d93fc7be5f8
- >= 69e3c75f4d541a6eb151b3ef91f34033cb3ad6e1, < e79f59a8527a49078cfaf8fe8fb5fcefc20c76d2
- >= 69e3c75f4d541a6eb151b3ef91f34033cb3ad6e1, < d85d2fd54e901637c81d847811e03c662aee13cd
- >= 69e3c75f4d541a6eb151b3ef91f34033cb3ad6e1, < 016763e829cac37b3234eace86fd0a4c560de4a7
- >= 69e3c75f4d541a6eb151b3ef91f34033cb3ad6e1, < 27e068d1b35dbec10a3cf268887c94407be4badc
- >= 69e3c75f4d541a6eb151b3ef91f34033cb3ad6e1, < d48ea5c9c4c34dc0df621f0e39ed3a16b644621a
- >= 69e3c75f4d541a6eb151b3ef91f34033cb3ad6e1, < 21b5953e7494c16a42e6cd8cf110e18d13ae4a6b
Fixed in 9c7e8ff48c377bef18c3d178748aea0575b69ede, 2a73b2c37ee3060a880b53cd24783d93fc7be5f8, e79f59a8527a49078cfaf8fe8fb5fcefc20c76d2, d85d2fd54e901637c81d847811e03c662aee13cd, 016763e829cac37b3234eace86fd0a4c560de4a7, 27e068d1b35dbec10a3cf268887c94407be4badc, d48ea5c9c4c34dc0df621f0e39ed3a16b644621a, 21b5953e7494c16a42e6cd8cf110e18d13ae4a6b
- 2.6.31
Fixed in 0, 5.10.267, 5.15.218, 6.1.185, 6.6.152, 6.12.104, 6.18.45, 7.1.9, 7.2
Mitigation
Upgrade Linux to 9c7e8ff48c377bef18c3d178748aea0575b69ede or 2a73b2c37ee3060a880b53cd24783d93fc7be5f8 or e79f59a8527a49078cfaf8fe8fb5fcefc20c76d2 or d85d2fd54e901637c81d847811e03c662aee13cd or 016763e829cac37b3234eace86fd0a4c560de4a7 or 27e068d1b35dbec10a3cf268887c94407be4badc or d48ea5c9c4c34dc0df621f0e39ed3a16b644621a or 21b5953e7494c16a42e6cd8cf110e18d13ae4a6b or later.
Upgrade Linux to 0 or 5.10.267 or 5.15.218 or 6.1.185 or 6.6.152 or 6.12.104 or 6.18.45 or 7.1.9 or 7.2 or later.
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.No PoC repositories found yet.