Answer in brief
CVE-2022-49340 records a High severity (CVSS 7.1) vulnerability in ip_gre: test csum_start instead of transport header. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
Answer in brief
CVE-2022-49340 records a High severity (CVSS 7.1) vulnerability in ip_gre: test csum_start instead of transport header. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 7.1. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Product | Affected versions | Fixed versions |
|---|---|---|
| cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:5.19:rc1:*:*:*:*:*:* | Not reported | Not reported |
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | 5.15 | Not reported |
| Linux/Linuxgeneric | >=774430026bd9a472d08c5d3c33351a782315771a <7596bd7920985f7fc8579a92e48bc53ce4475b21 || >=3d32ce5472bb2ca720bef84089b85f76a705fd1a <3d08bc3a5d9b2106f5c8bcf1adb73147824aa006 || >=87b34cd6485192777f632f92d592f2a71d8801a6 <fbeb8dfa8b87ef259eef0c89e39b53962a3cf604 || >=8a0ed250f911da31a2aef52101bc707846a800ff <e6b6f98fc7605c06c0a3baa70f62c534d7b4ce58 || >=8a0ed250f911da31a2aef52101bc707846a800ff <0c92d813c7c9ca2212ecd879232e7d87362fce98 || >=8a0ed250f911da31a2aef52101bc707846a800ff <0ffa268724656633af5f37a38c212326d98ebe8c || >=8a0ed250f911da31a2aef52101bc707846a800ff <8d21e9963bec1aad2280cdd034c8993033ef2948 || 4bf5d5224ffca069df4501ba5fcc6ded9c002ead || >=4.19.207 <4.19.247 || >=5.4.148 <5.4.198 || >=5.10.68 <5.10.122 || >=5.14.7 <5.15 | 7596bd7920985f7fc8579a92e48bc53ce4475b21, 3d08bc3a5d9b2106f5c8bcf1adb73147824aa006, fbeb8dfa8b87ef259eef0c89e39b53962a3cf604, e6b6f98fc7605c06c0a3baa70f62c534d7b4ce58, 0c92d813c7c9ca2212ecd879232e7d87362fce98, 0ffa268724656633af5f37a38c212326d98ebe8c, 8d21e9963bec1aad2280cdd034c8993033ef2948, 4.19.247, 5.4.198, 5.10.122, 5.15 |
Published upstream
Feb 26, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 4, 2026
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.
Quoted source text, attributed separately from HOL analysis.
CVSS is 7.1. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Product | Affected versions | Fixed versions |
|---|---|---|
| cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:5.19:rc1:*:*:*:*:*:* | Not reported | Not reported |
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | 5.15 | Not reported |
| Linux/Linuxgeneric | >=774430026bd9a472d08c5d3c33351a782315771a <7596bd7920985f7fc8579a92e48bc53ce4475b21 || >=3d32ce5472bb2ca720bef84089b85f76a705fd1a <3d08bc3a5d9b2106f5c8bcf1adb73147824aa006 || >=87b34cd6485192777f632f92d592f2a71d8801a6 <fbeb8dfa8b87ef259eef0c89e39b53962a3cf604 || >=8a0ed250f911da31a2aef52101bc707846a800ff <e6b6f98fc7605c06c0a3baa70f62c534d7b4ce58 || >=8a0ed250f911da31a2aef52101bc707846a800ff <0c92d813c7c9ca2212ecd879232e7d87362fce98 || >=8a0ed250f911da31a2aef52101bc707846a800ff <0ffa268724656633af5f37a38c212326d98ebe8c || >=8a0ed250f911da31a2aef52101bc707846a800ff <8d21e9963bec1aad2280cdd034c8993033ef2948 || 4bf5d5224ffca069df4501ba5fcc6ded9c002ead || >=4.19.207 <4.19.247 || >=5.4.148 <5.4.198 || >=5.10.68 <5.10.122 || >=5.14.7 <5.15 | 7596bd7920985f7fc8579a92e48bc53ce4475b21, 3d08bc3a5d9b2106f5c8bcf1adb73147824aa006, fbeb8dfa8b87ef259eef0c89e39b53962a3cf604, e6b6f98fc7605c06c0a3baa70f62c534d7b4ce58, 0c92d813c7c9ca2212ecd879232e7d87362fce98, 0ffa268724656633af5f37a38c212326d98ebe8c, 8d21e9963bec1aad2280cdd034c8993033ef2948, 4.19.247, 5.4.198, 5.10.122, 5.15 |
Published upstream
Feb 26, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 4, 2026
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.
Quoted source text, attributed separately from HOL analysis.