Answer in brief
CVE-2024-49978 records a Unknown severity vulnerability in gso: fix udp gso fraglist segmentation after pull from frag_list. 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.
A CVSS score is not reported in the current record. 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.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=9fd1ff5d2ac7181844735806b0a703c942365291 <080e6c9a3908de193a48f646c5ce1bfb15676ffc || >=9fd1ff5d2ac7181844735806b0a703c942365291 <af3122f5fdc0d00581d6e598a668df6bf54c9daa || >=9fd1ff5d2ac7181844735806b0a703c942365291 <33e28acf42ee863f332a958bfc2f1a284a3659df || >=9fd1ff5d2ac7181844735806b0a703c942365291 <3cd00d2e3655fad3bda96dc1ebf17b6495f86fea || >=9fd1ff5d2ac7181844735806b0a703c942365291 <a1e40ac5b5e9077fe1f7ae0eb88034db0f9ae1ab | 080e6c9a3908de193a48f646c5ce1bfb15676ffc, af3122f5fdc0d00581d6e598a668df6bf54c9daa, 33e28acf42ee863f332a958bfc2f1a284a3659df, 3cd00d2e3655fad3bda96dc1ebf17b6495f86fea, a1e40ac5b5e9077fe1f7ae0eb88034db0f9ae1ab |
| Linux/Linuxgeneric | 5.6 | Not reported |
Published upstream
Oct 21, 2024
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
In the Linux kernel, the following vulnerability has been resolved: gso: fix udp gso fraglist segmentation after pull from frag_list Detect gso fraglist skbs with corrupted geometry (see below) and pass these to skb_segment instead of skb_segment_list, as the first can segment them correctly. Valid SKB_GSO_FRAGLIST skbs - consist of two or more segments - the head_skb holds the protocol headers plus first gso_size - one or more frag_list skbs hold exactly one segment - all but the last must be gso_size Optional datapath hooks such as NAT and BPF (bpf_skb_pull_data) can modify these skbs, breaking these invariants. In extreme cases they pull all data into skb linear. For UDP, this causes a NULL ptr deref in __udpv4_gso_segment_list_csum at udp_hdr(seg->next)->dest. Detect invalid geometry due to pull, by checking head_skb size. Don't just drop, as this may blackhole a destination. Convert to be able to pass to regular skb_segment.
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2024-49978 records a Unknown severity vulnerability in gso: fix udp gso fraglist segmentation after pull from frag_list. 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.
A CVSS score is not reported in the current record. 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.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=9fd1ff5d2ac7181844735806b0a703c942365291 <080e6c9a3908de193a48f646c5ce1bfb15676ffc || >=9fd1ff5d2ac7181844735806b0a703c942365291 <af3122f5fdc0d00581d6e598a668df6bf54c9daa || >=9fd1ff5d2ac7181844735806b0a703c942365291 <33e28acf42ee863f332a958bfc2f1a284a3659df || >=9fd1ff5d2ac7181844735806b0a703c942365291 <3cd00d2e3655fad3bda96dc1ebf17b6495f86fea || >=9fd1ff5d2ac7181844735806b0a703c942365291 <a1e40ac5b5e9077fe1f7ae0eb88034db0f9ae1ab | 080e6c9a3908de193a48f646c5ce1bfb15676ffc, af3122f5fdc0d00581d6e598a668df6bf54c9daa, 33e28acf42ee863f332a958bfc2f1a284a3659df, 3cd00d2e3655fad3bda96dc1ebf17b6495f86fea, a1e40ac5b5e9077fe1f7ae0eb88034db0f9ae1ab |
| Linux/Linuxgeneric | 5.6 | Not reported |
Published upstream
Oct 21, 2024
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
In the Linux kernel, the following vulnerability has been resolved: gso: fix udp gso fraglist segmentation after pull from frag_list Detect gso fraglist skbs with corrupted geometry (see below) and pass these to skb_segment instead of skb_segment_list, as the first can segment them correctly. Valid SKB_GSO_FRAGLIST skbs - consist of two or more segments - the head_skb holds the protocol headers plus first gso_size - one or more frag_list skbs hold exactly one segment - all but the last must be gso_size Optional datapath hooks such as NAT and BPF (bpf_skb_pull_data) can modify these skbs, breaking these invariants. In extreme cases they pull all data into skb linear. For UDP, this causes a NULL ptr deref in __udpv4_gso_segment_list_csum at udp_hdr(seg->next)->dest. Detect invalid geometry due to pull, by checking head_skb size. Don't just drop, as this may blackhole a destination. Convert to be able to pass to regular skb_segment.
Quoted source text, attributed separately from HOL analysis.