ip_gre: test csum_start instead of transport header
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel e6b6f98fc7605c06c0a3baa70f62c534d7b4ce58, Kernel 5.15, Kernel 5.4.198 and 11 more.
In the Linux kernel, the following vulnerability has been resolved: ip_gre: test csum_start instead of transport header GRE with TUNNEL_CSUM will apply local checksum offload on CHECKSUM_PARTIAL packets. ipgre_xmit must validate csum_start after an optional skb_pull, else lco_csum may trigger an overflow. The original check was if (csum && skb_checksum_start(skb) < skb->data) return -EINVAL; This had false positives when skb_checksum_start is undefined: when ip_summed is not CHECKSUM_PARTIAL. A discussed refinement was straightforward if (csum && skb->ip_summed == CHECKSUM_PARTIAL && skb_checksum_start(skb) < skb->data) return -EINVAL; But was eventually revised more thoroughly: - restrict the check to the only branch where needed, in an uncommon GRE path that uses header_ops and calls skb_pull. - test skb_transport_header, which is set along with csum_start in skb_partial_csum_set in the normal header_ops datapath. Turns out skbs can arrive in this branch without the transport header set, e.g., through BPF redirection. Revise the check back to check csum_start directly, and only if CHECKSUM_PARTIAL. Do leave the check in the updated location. Check field regardless of whether TUNNEL_CSUM is configured.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | >=8a0ed250f911da31a2aef52101bc707846a800ff <e6b6f98fc7605c06c0a3baa70f62c534d7b4ce58, >=5.14.7 <5.15, >=5.4.148 <5.4.198, >=774430026bd9a472d08c5d3c33351a782315771a <7596bd7920985f7fc8579a92e48bc53ce4475b21, >=87b34cd6485192777f632f92d592f2a71d8801a6 <fbeb8dfa8b87ef259eef0c89e39b53962a3cf604, >=8a0ed250f911da31a2aef52101bc707846a800ff <0c92d813c7c9ca2212ecd879232e7d87362fce98, >=8a0ed250f911da31a2aef52101bc707846a800ff <0ffa268724656633af5f37a38c212326d98ebe8c, >=8a0ed250f911da31a2aef52101bc707846a800ff <8d21e9963bec1aad2280cdd034c8993033ef2948, =4bf5d5224ffca069df4501ba5fcc6ded9c002ead, =5.15, >=3d32ce5472bb2ca720bef84089b85f76a705fd1a <3d08bc3a5d9b2106f5c8bcf1adb73147824aa006, >=4.19.207 <4.19.247, >=5.10.68 <5.10.122 | e6b6f98fc7605c06c0a3baa70f62c534d7b4ce58, 5.15, 5.4.198, 7596bd7920985f7fc8579a92e48bc53ce4475b21, fbeb8dfa8b87ef259eef0c89e39b53962a3cf604, 0c92d813c7c9ca2212ecd879232e7d87362fce98, 0ffa268724656633af5f37a38c212326d98ebe8c, 8d21e9963bec1aad2280cdd034c8993033ef2948, 3d08bc3a5d9b2106f5c8bcf1adb73147824aa006, 4.19.247, 5.10.122 |
| linux-kernel: Kernel | >=5.10.68 <5.10.122, >=5.14.7 <5.15, >=5.15.0 <5.15.47, >=5.16.0 <5.17.15, >=5.18.0 <5.18.4, >=5.4.148 <5.4.198, >=4.19.207 <4.19.247 | 5.10.122, 5.15, 5.15.47, 5.17.15, 5.18.4, 5.4.198, 4.19.247 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket