8.8
CVE-2024-35884
- EPSS 0.06%
- Veröffentlicht 19.05.2024 09:15:09
- Zuletzt bearbeitet 21.11.2024 09:21:07
- Quelle 416baaa9-dc9f-4396-8d5f-8c081f
- Teams Watchlist Login
- Unerledigt Login
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
Verknüpft mit AI von unstrukturierten Daten zu bestehenden CPE der NVD
Diese Information steht angemeldeten Benutzern zur Verfügung. Login
Daten sind bereitgestellt durch das CVE Programm von einer CVE Numbering Authority (CNA) (Unstrukturiert).
HerstellerLinux
≫
Produkt
Linux
Default Statusunaffected
Version <
3391b157780bbedf8ef9f202cbf10ee90bf6b0f8
Version
9fd1ff5d2ac7181844735806b0a703c942365291
Status
affected
Version <
d49ae15a5767d4e9ef8bbb79e42df1bfebc94670
Version
9fd1ff5d2ac7181844735806b0a703c942365291
Status
affected
Version <
d12245080cb259d82b34699f6cd4ec11bdb688bd
Version
9fd1ff5d2ac7181844735806b0a703c942365291
Status
affected
Version <
3001e7aa43d6691db2a878b0745b854bf12ddd19
Version
9fd1ff5d2ac7181844735806b0a703c942365291
Status
affected
Version <
35fe0e0b5c00bef7dde74842a2564c43856fbce4
Version
9fd1ff5d2ac7181844735806b0a703c942365291
Status
affected
Version <
3d010c8031e39f5fa1e8b13ada77e0321091011f
Version
9fd1ff5d2ac7181844735806b0a703c942365291
Status
affected
HerstellerLinux
≫
Produkt
Linux
Default Statusaffected
Version
5.6
Status
affected
Version <
5.6
Version
0
Status
unaffected
Version <=
5.10.*
Version
5.10.215
Status
unaffected
Version <=
5.15.*
Version
5.15.154
Status
unaffected
Version <=
6.1.*
Version
6.1.85
Status
unaffected
Version <=
6.6.*
Version
6.6.26
Status
unaffected
Version <=
6.8.*
Version
6.8.5
Status
unaffected
Version <=
*
Version
6.9
Status
unaffected
Zu dieser CVE wurde keine CISA KEV oder CERT.AT-Warnung gefunden.
Typ | Quelle | Score | Percentile |
---|---|---|---|
EPSS | FIRST.org | 0.06% | 0.177 |
Quelle | Base Score | Exploit Score | Impact Score | Vector String |
---|---|---|---|---|
134c704f-9b21-4f2e-91b3-4a467353bcc0 | 8.8 | 2.8 | 5.9 |
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
|