Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2024-35884: udp: do not accept non-tunnel GSO skbs landing in a tunnel

Noroxi assessment

Priority: Monitor (action score 22/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.68% (FIRST EPSS); higher than 52.9% of all records.
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: Linux Linux 3001e7aa43d6691db2a878b0745b854bf12ddd19, 3391b157780bbedf8ef9f202cbf10ee90bf6b0f8, 35fe0e0b5c00bef7dde74842a2564c43856fbce4.
  • Severity is disputed: the assigning authority (CNA) scores it 9.8, NVD 5.5.
  • Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to Linux Linux 3001e7aa43d6691db2a878b0745b854bf12ddd19, 3391b157780bbedf8ef9f202cbf10ee90bf6b0f8, 35fe0e0b5c00bef7dde74842a2564c43856fbce4 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

In the Linux kernel, the following vulnerability has been resolved: udp: do not accept non-tunnel GSO skbs landing in a tunnel When rx-udp-gro-forwarding is enabled UDP packets might be GROed when being forwarded. If such packets might land in a tunnel this can cause various issues and udp_gro_receive makes sure this isn't the case by looking for a matching socket. This is performed in udp4/6_gro_lookup_skb but only in the current netns. This is an issue with tunneled packets when the endpoint is in another netns. In such cases the packets will be GROed at the UDP level, which leads to various issues later on. The same thing can happen with rx-gro-list. We saw this with geneve packets being GROed at the UDP level. In such case gso_size is set; later the packet goes through the geneve rx path, the geneve header is pulled, the offset are adjusted and frag_list skbs are not adjusted with regard to geneve. When those skbs hit skb_fragment, it will misbehave. Different outcomes are possible depending on what the GROed skbs look like; from corrupted packets to kernel crashes. One example is a BUG_ON[1] triggered in skb_segment while processing the frag_list. Because gso_size is wrong (geneve header was pulled) skb_segment thinks there is "geneve header size" of data in frag_list, although it's in fact the next packet. The BUG_ON itself has nothing to do with the issue. This is only one of the potential issues. Looking up for a matching socket in udp_gro_receive is fragile: the lookup could be extended to all netns (not speaking about performances) but nothing prevents those packets from being modified in between and we could still not find a matching socket. It's OK to keep the current logic there as it should cover most cases but we also need to make sure we handle tunnel packets being GROed too early. This is done by extending the checks in udp_unexpected_gso: GSO packets lacking the SKB_GSO_UDP_TUNNEL/_CSUM bits and landing in a tunnel must be segmented. [1] kernel BUG at net/core/skbuff.c:4408! RIP: 0010:skb_segment+0xd2a/0xf70 __udp_gso_segment+0xaa/0x560

MediumCVSS 5.5 · v3.1—No exploit Fix available
Published
May 19, 2024
Updated
Oct 15, 2026
EPSS
0.6% · 52th percentile

Report tools

JSON

Action score

22

Monitor

Low priority for now.

CVSS
22 / 40 · 5.5 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.6%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
5.5
CNA · Linux
9.8
4.3 point gap

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2024-35884

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
linuxlinux kernel
debiandebian linux

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • debian debian linux10.0
  • linux linux kernel5.11 and later · before 5.15.154
  • linux linux kernel5.16 and later · before 6.1.85
  • linux linux kernel5.6 and later · before 5.10.215
  • linux linux kernel6.7 and later · before 6.8.5
  • linux linux kernel6.2 and later · before 6.6.26
  • linux linux kernel6.9

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 5.6affected
    • 9fd1ff5d2ac7181844735806b0a703c942365291 and later · before 3391b157780bbedf8ef9f202cbf10ee90bf6b0f8affected · git
    • 9fd1ff5d2ac7181844735806b0a703c942365291 and later · before d49ae15a5767d4e9ef8bbb79e42df1bfebc94670affected · git
    • 9fd1ff5d2ac7181844735806b0a703c942365291 and later · before d12245080cb259d82b34699f6cd4ec11bdb688bdaffected · git
    • 9fd1ff5d2ac7181844735806b0a703c942365291 and later · before 3001e7aa43d6691db2a878b0745b854bf12ddd19affected · git
    • 9fd1ff5d2ac7181844735806b0a703c942365291 and later · before 35fe0e0b5c00bef7dde74842a2564c43856fbce4affected · git
    • 9fd1ff5d2ac7181844735806b0a703c942365291 and later · before 3d010c8031e39f5fa1e8b13ada77e0321091011faffected · git
    • before 5.6not affected · semver
    • 5.10.215 and later · up to and including 5.10.*not affected · semver
    • 5.15.154 and later · up to and including 5.15.*not affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.85-16.1.85-1
Debian:13linuxbefore 6.8.9-16.8.9-1
Red Hat:rhel_aus:8.6::baseosbpftoolbefore 0:4.18.0-372.126.1.el8_60:4.18.0-372.126.1.el8_6
Red Hat:rhel_aus:8.6::baseosbpftool-debuginfobefore 0:4.18.0-372.126.1.el8_60:4.18.0-372.126.1.el8_6
Red Hat:rhel_aus:8.6::baseoskernelbefore 0:4.18.0-372.126.1.el8_60:4.18.0-372.126.1.el8_6
Red Hat:rhel_aus:8.6::baseoskernel-abi-stablelistsbefore 0:4.18.0-372.126.1.el8_60:4.18.0-372.126.1.el8_6
Red Hat:rhel_aus:8.6::baseoskernel-corebefore 0:4.18.0-372.126.1.el8_60:4.18.0-372.126.1.el8_6
Red Hat:rhel_aus:8.6::baseoskernel-debugbefore 0:4.18.0-372.126.1.el8_60:4.18.0-372.126.1.el8_6
Red Hat:rhel_aus:8.6::baseoskernel-debug-corebefore 0:4.18.0-372.126.1.el8_60:4.18.0-372.126.1.el8_6
Red Hat:rhel_aus:8.6::baseoskernel-debug-debuginfobefore 0:4.18.0-372.126.1.el8_60:4.18.0-372.126.1.el8_6
Red Hat:rhel_aus:8.6::baseoskernel-debug-develbefore 0:4.18.0-372.126.1.el8_60:4.18.0-372.126.1.el8_6
Red Hat:rhel_aus:8.6::baseoskernel-debug-modulesbefore 0:4.18.0-372.126.1.el8_60:4.18.0-372.126.1.el8_6
Red Hat:rhel_aus:8.6::baseoskernel-debug-modules-extrabefore 0:4.18.0-372.126.1.el8_60:4.18.0-372.126.1.el8_6
Red Hat:rhel_aus:8.6::baseoskernel-debuginfobefore 0:4.18.0-372.126.1.el8_60:4.18.0-372.126.1.el8_6
Red Hat:rhel_aus:8.6::baseoskernel-debuginfo-common-x86_64before 0:4.18.0-372.126.1.el8_60:4.18.0-372.126.1.el8_6
Red Hat:rhel_aus:8.6::baseoskernel-develbefore 0:4.18.0-372.126.1.el8_60:4.18.0-372.126.1.el8_6
Red Hat:rhel_aus:8.6::baseoskernel-docbefore 0:4.18.0-372.126.1.el8_60:4.18.0-372.126.1.el8_6
Red Hat:rhel_aus:8.6::baseoskernel-modulesbefore 0:4.18.0-372.126.1.el8_60:4.18.0-372.126.1.el8_6
Red Hat:rhel_aus:8.6::baseoskernel-modules-extrabefore 0:4.18.0-372.126.1.el8_60:4.18.0-372.126.1.el8_6
Red Hat:rhel_aus:8.6::baseoskernel-toolsbefore 0:4.18.0-372.126.1.el8_60:4.18.0-372.126.1.el8_6
Red Hat:rhel_aus:8.6::baseoskernel-tools-debuginfobefore 0:4.18.0-372.126.1.el8_60:4.18.0-372.126.1.el8_6
Red Hat:rhel_aus:8.6::baseoskernel-tools-libsbefore 0:4.18.0-372.126.1.el8_60:4.18.0-372.126.1.el8_6
Red Hat:rhel_aus:8.6::baseosperfbefore 0:4.18.0-372.126.1.el8_60:4.18.0-372.126.1.el8_6
Red Hat:rhel_aus:8.6::baseosperf-debuginfobefore 0:4.18.0-372.126.1.el8_60:4.18.0-372.126.1.el8_6

+45

Same product

linux: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
    90Now
  • CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV
    89Now
  • CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
    85Now

Published before and after this one in the same product

  • ← EarlierCVE-2024-35860May 19, 2024 · bpf: support deferring bpf_link dealloc to after RCU grace period
    22Monitor
  • ← EarlierCVE-2024-35877May 19, 2024 · x86/mm/pat: fix VM_PAT handling in COW mappings
    22Monitor
  • Later →CVE-2024-35886May 19, 2024 · ipv6: Fix infinite recursion in fib6_dump_done().
    31Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux3001e7aa43d6691db2a878b0745b854bf12ddd19Vendor (CNA)
Linux Linux3391b157780bbedf8ef9f202cbf10ee90bf6b0f8Vendor (CNA)
Linux Linux35fe0e0b5c00bef7dde74842a2564c43856fbce4Vendor (CNA)
Linux Linux3d010c8031e39f5fa1e8b13ada77e0321091011fVendor (CNA)
Linux Linuxd12245080cb259d82b34699f6cd4ec11bdb688bdVendor (CNA)
Linux Linuxd49ae15a5767d4e9ef8bbb79e42df1bfebc94670Vendor (CNA)
debian:linux6.1.85-1 · Debian:12Package registry (OSV)
red hat:bpftool0:4.18.0-477.75.1.el8_8 · Red Hat:rhel_eus:8.8::baseosPackage registry (OSV)
red hat:bpftool-debuginfo0:4.18.0-477.75.1.el8_8 · Red Hat:rhel_eus:8.8::baseosPackage registry (OSV)
red hat:kernel0:4.18.0-477.75.1.el8_8 · Red Hat:rhel_eus:8.8::baseosPackage registry (OSV)
red hat:kernel-abi-stablelists0:4.18.0-477.75.1.el8_8 · Red Hat:rhel_eus:8.8::baseosPackage registry (OSV)
red hat:kernel-core0:4.18.0-477.75.1.el8_8 · Red Hat:rhel_eus:8.8::baseosPackage registry (OSV)
red hat:kernel-debug0:4.18.0-477.75.1.el8_8 · Red Hat:rhel_eus:8.8::baseosPackage registry (OSV)
red hat:kernel-debug-core0:4.18.0-477.75.1.el8_8 · Red Hat:rhel_eus:8.8::baseosPackage registry (OSV)
red hat:kernel-debug-debuginfo0:4.18.0-477.75.1.el8_8 · Red Hat:rhel_eus:8.8::baseosPackage registry (OSV)
red hat:kernel-debug-devel0:4.18.0-477.75.1.el8_8 · Red Hat:rhel_eus:8.8::baseosPackage registry (OSV)
red hat:kernel-debug-modules0:4.18.0-477.75.1.el8_8 · Red Hat:rhel_eus:8.8::baseosPackage registry (OSV)
red hat:kernel-debug-modules-extra0:4.18.0-477.75.1.el8_8 · Red Hat:rhel_eus:8.8::baseosPackage registry (OSV)
red hat:kernel-debuginfo0:4.18.0-477.75.1.el8_8 · Red Hat:rhel_eus:8.8::baseosPackage registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

  • CVE-2023-2156376 days apartA flaw was found in the networking subsystem of the Linux kernel within the handling of the RPL protocol.
    32Monitor
  • CVE-2023-5262154 days apartbpf: Check rcu_read_lock_trace_held() before calling bpf map helpers
    31Monitor
  • CVE-2025-39803484 days apartscsi: ufs: core: Remove WARN_ON_ONCE() call from ufshcd_uic_cmd_compl()
    31Monitor
  • CVE-2024-359571 days apartiommu/vt-d: Fix WARN_ON in iommu probe path
    22Monitor
  • CVE-2024-360001 days apartmm/hugetlb: fix missing hugetlb_lock for resv uncharge
    22Monitor
  • CVE-2021-473512 days apartubifs: Fix races between xattr_{set|get} and listxattr operations
    22Monitor

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

National notice (Türkiye Cybersecurity Directorate / USOM)

Official security notices citing this record; remediation advice is on the agency's page.

All national notices →

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
none
Integrity
none
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
None
Integrity impact
None
Availability impact
High

Weakness class (CWE)

CWE-617 · Reachable Assertion

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (7 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records