packet: use consistent hard_header_len in TX_RING send path
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 016763e829cac37b3234eace86fd0a4c560de4a7, Kernel 21b5953e7494c16a42e6cd8cf110e18d13ae4a6b, Kernel 27e068d1b35dbec10a3cf268887c94407be4badc and 5 more.
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
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | =2.6.31, >=69e3c75f4d541a6eb151b3ef91f34033cb3ad6e1 <016763e829cac37b3234eace86fd0a4c560de4a7, >=69e3c75f4d541a6eb151b3ef91f34033cb3ad6e1 <21b5953e7494c16a42e6cd8cf110e18d13ae4a6b, >=69e3c75f4d541a6eb151b3ef91f34033cb3ad6e1 <27e068d1b35dbec10a3cf268887c94407be4badc, >=69e3c75f4d541a6eb151b3ef91f34033cb3ad6e1 <2a73b2c37ee3060a880b53cd24783d93fc7be5f8, >=69e3c75f4d541a6eb151b3ef91f34033cb3ad6e1 <9c7e8ff48c377bef18c3d178748aea0575b69ede, >=69e3c75f4d541a6eb151b3ef91f34033cb3ad6e1 <d48ea5c9c4c34dc0df621f0e39ed3a16b644621a, >=69e3c75f4d541a6eb151b3ef91f34033cb3ad6e1 <d85d2fd54e901637c81d847811e03c662aee13cd, >=69e3c75f4d541a6eb151b3ef91f34033cb3ad6e1 <e79f59a8527a49078cfaf8fe8fb5fcefc20c76d2 | 016763e829cac37b3234eace86fd0a4c560de4a7, 21b5953e7494c16a42e6cd8cf110e18d13ae4a6b, 27e068d1b35dbec10a3cf268887c94407be4badc, 2a73b2c37ee3060a880b53cd24783d93fc7be5f8, 9c7e8ff48c377bef18c3d178748aea0575b69ede, d48ea5c9c4c34dc0df621f0e39ed3a16b644621a, d85d2fd54e901637c81d847811e03c662aee13cd, e79f59a8527a49078cfaf8fe8fb5fcefc20c76d2 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket