CVE-2022-49340
published 2025-02-26CVE-2022-49340: 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…
PriorityP420medium5.5CVSS 3.1
AVLACLPRLUINSUCNINAH
EPSS
0.28%
20.4th percentile
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) 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) 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
25 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| debian | linux | < linux 5.18.5-1 (bookworm) | linux 5.18.5-1 (bookworm) |
| linux | linux | — | — |
| linux | linux | — | — |
| linux | linux | >= 3d32ce5472bb2ca720bef84089b85f76a705fd1a < 3d08bc3a5d9b2106f5c8bcf1adb73147824aa006 | 3d08bc3a5d9b2106f5c8bcf1adb73147824aa006 |
| linux | linux | >= 4.19.207 < 4.19.247 | 4.19.247 |
| linux | linux | >= 5.10.68 < 5.10.122 | 5.10.122 |
| linux | linux | >= 5.14.7 < 5.15 | 5.15 |
| linux | linux | >= 5.4.148 < 5.4.198 | 5.4.198 |
| linux | linux | >= 774430026bd9a472d08c5d3c33351a782315771a < 7596bd7920985f7fc8579a92e48bc53ce4475b21 | 7596bd7920985f7fc8579a92e48bc53ce4475b21 |
| linux | linux | >= 87b34cd6485192777f632f92d592f2a71d8801a6 < fbeb8dfa8b87ef259eef0c89e39b53962a3cf604 | fbeb8dfa8b87ef259eef0c89e39b53962a3cf604 |
| linux | linux | >= 8a0ed250f911da31a2aef52101bc707846a800ff < e6b6f98fc7605c06c0a3baa70f62c534d7b4ce58 | e6b6f98fc7605c06c0a3baa70f62c534d7b4ce58 |
| linux | linux | >= 8a0ed250f911da31a2aef52101bc707846a800ff < 0c92d813c7c9ca2212ecd879232e7d87362fce98 | 0c92d813c7c9ca2212ecd879232e7d87362fce98 |
| linux | linux | >= 8a0ed250f911da31a2aef52101bc707846a800ff < 0ffa268724656633af5f37a38c212326d98ebe8c | 0ffa268724656633af5f37a38c212326d98ebe8c |
| linux | linux | >= 8a0ed250f911da31a2aef52101bc707846a800ff < 8d21e9963bec1aad2280cdd034c8993033ef2948 | 8d21e9963bec1aad2280cdd034c8993033ef2948 |
| linux | linux_kernel | — | — |
| linux | linux_kernel | >= 0 < 5.10.127-1 | 5.10.127-1 |
| linux | linux_kernel | >= 0 < 5.18.5-1 | 5.18.5-1 |
| linux | linux_kernel | >= 0 < 5.18.5-1 | 5.18.5-1 |
| linux | linux_kernel | >= 0 < 5.18.5-1 | 5.18.5-1 |
| linux | linux_kernel | >= 4.19.207 < 4.19.247 | 4.19.247 |
| linux | linux_kernel | >= 5.10.68 < 5.10.122 | 5.10.122 |
| linux | linux_kernel | >= 5.14.7 < 5.15.47 | 5.15.47 |
| linux | linux_kernel | >= 5.16 < 5.17.15 | 5.17.15 |
| linux | linux_kernel | >= 5.18 < 5.18.4 | 5.18.4 |
| linux | linux_kernel | >= 5.4.148 < 5.4.198 | 5.4.198 |
CVSS provenance
nvdv3.15.5MEDIUMCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
osv5.5MEDIUM
vendor_debian5.5MEDIUM
vendor_redhat5.5MEDIUM
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
Red Hat
kernel: ip_gre: test csum_start instead of transport header
vendor_redhat·2025-02-26·CVSS 5.5
CVE-2022-49340 [MEDIUM] kernel: ip_gre: test csum_start instead of transport header
kernel: ip_gre: test csum_start instead of transport header
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) 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) data)
return -EINVAL;
But was eventually revised more thoroughly:
- restrict the check to the only branch where needed, in an
uncom
Debian
CVE-2022-49340: linux - In the Linux kernel, the following vulnerability has been resolved: ip_gre: tes...
vendor_debian·2022·CVSS 5.5
CVE-2022-49340 [MEDIUM] CVE-2022-49340: linux - In the Linux kernel, the following vulnerability has been resolved: ip_gre: tes...
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) 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) 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
GHSA
GHSA-4qqr-2jj8-h8q8: In the Linux kernel, the following vulnerability has been resolved:
ip_gre: test csum_start instead of transport header
GRE with TUNNEL_CSUM will ap
ghsa_unreviewed·2025-10-21
CVE-2022-49340 [MEDIUM] GHSA-4qqr-2jj8-h8q8: In the Linux kernel, the following vulnerability has been resolved:
ip_gre: test csum_start instead of transport header
GRE with TUNNEL_CSUM will ap
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) 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) 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.
OSV
CVE-2022-49340: In the Linux kernel, the following vulnerability has been resolved: ip_gre: test csum_start instead of transport header GRE with TUNNEL_CSUM will appl
osv·2025-02-26·CVSS 5.5
CVE-2022-49340 [MEDIUM] CVE-2022-49340: In the Linux kernel, the following vulnerability has been resolved: ip_gre: test csum_start instead of transport header GRE with TUNNEL_CSUM will appl
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) 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) 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
No detection rules found.
No public exploits indexed.
https://git.kernel.org/stable/c/0c92d813c7c9ca2212ecd879232e7d87362fce98https://git.kernel.org/stable/c/0ffa268724656633af5f37a38c212326d98ebe8chttps://git.kernel.org/stable/c/3d08bc3a5d9b2106f5c8bcf1adb73147824aa006https://git.kernel.org/stable/c/7596bd7920985f7fc8579a92e48bc53ce4475b21https://git.kernel.org/stable/c/8d21e9963bec1aad2280cdd034c8993033ef2948https://git.kernel.org/stable/c/e6b6f98fc7605c06c0a3baa70f62c534d7b4ce58https://git.kernel.org/stable/c/fbeb8dfa8b87ef259eef0c89e39b53962a3cf604
2025-02-26
Published