Goal Reached Thanks to every supporter — we hit 100%!

Goal: 1000 CNY · Raised: 1000 CNY

100.0%

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

EPSS 0.02% · P5
Get alerts for future matching vulnerabilitiesLog in to subscribe

I. Basic Information for CVE-2024-35884

Vulnerability Information

Have questions about the vulnerability? See if Shenlong's analysis helps!
View Shenlong Deep Dive ↗

Although we use advanced large model technology, its output may still contain inaccurate or outdated information.Shenlong tries to ensure data accuracy, but please verify and judge based on the actual situation.

Vulnerability Title
udp: do not accept non-tunnel GSO skbs landing in a tunnel
Source: NVD (National Vulnerability Database)
Vulnerability Description
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
Source: NVD (National Vulnerability Database)
CVSS Information
N/A
Source: NVD (National Vulnerability Database)
Vulnerability Type
N/A
Source: NVD (National Vulnerability Database)
Vulnerability Title
Linux kernel 安全漏洞
Source: CNNVD (China National Vulnerability Database)
Vulnerability Description
Linux kernel是美国Linux基金会的开源操作系统Linux所使用的内核。 Linux kernel存在安全漏洞,该漏洞源于允许非隧道 GSO skbs 在隧道中登陆。
Source: CNNVD (China National Vulnerability Database)
CVSS Information
N/A
Source: CNNVD (China National Vulnerability Database)
Vulnerability Type
N/A
Source: CNNVD (China National Vulnerability Database)

Affected Products

VendorProductAffected VersionsCPESubscribe
LinuxLinux 9fd1ff5d2ac7181844735806b0a703c942365291 ~ 3391b157780bbedf8ef9f202cbf10ee90bf6b0f8 -
LinuxLinux 5.6 -

II. Public POCs for CVE-2024-35884

#POC DescriptionSource LinkShenlong Link
AI-Generated POCPremium

No public POC found.

Login to generate AI POC

III. Intelligence Information for CVE-2024-35884

登录查看更多情报信息。

Same Patch Batch · Linux · 2024-05-19 · 82 CVEs total

CVE-2024-35915nfc: nci: Fix uninit-value in nci_dev_up and nci_ntf_packet
CVE-2024-35926crypto: iaa - Fix async_disable descriptor leak
CVE-2024-35912wifi: iwlwifi: mvm: rfi: fix potential response leaks
CVE-2024-35913wifi: iwlwifi: mvm: pick the version of SESSION_PROTECTION_NOTIF
CVE-2024-35911ice: fix memory corruption bug with suspend and rebuild
CVE-2024-35908tls: get psock ref after taking rxlock to avoid leak
CVE-2024-35907mlxbf_gige: call request_irq() after NAPI initialized
CVE-2024-35905bpf: Protect against int overflow for stack access size
CVE-2024-35904selinux: avoid dereference of garbage after mount failure
CVE-2024-35909net: wwan: t7xx: Split 64bit accesses to fix alignment issues
CVE-2024-35914nfsd: Fix error cleanup path in nfsd_rename()
CVE-2024-35916dma-buf: Fix NULL pointer dereference in sanitycheck()
CVE-2024-35917s390/bpf: Fix bpf_plt pointer arithmetic
CVE-2023-52699sysv: don't call sb_bread() with pointers_lock held
CVE-2024-35919media: mediatek: vcodec: adding lock to protect encoder context list
CVE-2024-35920media: mediatek: vcodec: adding lock to protect decoder context list
CVE-2024-35921media: mediatek: vcodec: Fix oops when HEVC init fails
CVE-2024-35922fbmon: prevent division by zero in fb_videomode_from_videomode()
CVE-2024-35924usb: typec: ucsi: Limit read size on v1.2
CVE-2024-35925block: prevent division by zero in blk_rq_stat_sum()

Showing top 20 of 82 CVEs. View all on vendor page → →

IV. Related Vulnerabilities

V. Comments for CVE-2024-35884

No comments yet


Leave a comment