net: gso: fix ownership in __udp_gso_segment
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 5.4.291, 5.10.235, 5.15.179, 6.1.131, 6.6.83, and 2 more
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
In the Linux kernel, the following vulnerability has been resolved: net: gso: fix ownership in __udp_gso_segment In __udp_gso_segment the skb destructor is removed before segmenting the skb but the socket reference is kept as-is. This is an issue if the original skb is later orphaned as we can hit the following bug: kernel BUG at ./include/linux/skbuff.h:3312! (skb_orphan) RIP: 0010:ip_rcv_core+0x8b2/0xca0 Call Trace: ip_rcv+0xab/0x6e0 __netif_receive_skb_one_core+0x168/0x1b0 process_backlog+0x384/0x1100 __napi_poll.constprop.0+0xa1/0x370 net_rx_action+0x925/0xe50 The above can happen following a sequence of events when using OpenVSwitch, when an OVS_ACTION_ATTR_USERSPACE action precedes an OVS_ACTION_ATTR_OUTPUT action: 1. OVS_ACTION_ATTR_USERSPACE is handled (in do_execute_actions): the skb goes through queue_gso_packets and then __udp_gso_segment, where its destructor is removed. 2. The segments' data are copied and sent to userspace. 3. OVS_ACTION_ATTR_OUTPUT is handled (in do_execute_actions) and the same original skb is sent to its path. 4. If it later hits skb_orphan, we hit the bug. Fix this by also removing the reference to the socket in __udp_gso_segment.
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
From ad405857b174ed31a97982bb129c320d03321cf5 · fixed in 9f28205ddb76e86cac418332e952241d85fed0dc; From ad405857b174ed31a97982bb129c320d03321cf5 · fixed in a2d1cca955ed34873e524cc2e6e885450d262f05; From ad405857b174ed31a97982bb129c320d03321cf5 · fixed in 455217ac9db0cf9349b3933664355e907bb1a569; From ad405857b174ed31a97982bb129c320d03321cf5 · fixed in e8db70537878e1bb3fd83e5abcc6feefc0587828; From ad405857b174ed31a97982bb129c320d03321cf5 · fixed in 01a83237644d6822bc7df2c5564fc81b0df84358; From ad405857b174ed31a97982bb129c320d03321cf5 · fixed in 084819b0d8b1bd433b90142371eb9450d657f8ca; From ad405857b174ed31a97982bb129c320d03321cf5 · fixed in c32da44cc9298eaa6109e3fc2c2b4e07cc4bf11b; From ad405857b174ed31a97982bb129c320d03321cf5 · fixed in ee01b2f2d7d0010787c2343463965bbc283a497f
- Linux Linux
4.18
- KernelLinux
From 4.18.0 · fixed in 5.4.291; From 5.5.0 · fixed in 5.10.235; From 5.11.0 · fixed in 5.15.179; From 5.16.0 · fixed in 6.1.131; From 6.2.0 · fixed in 6.6.83; From 6.7.0 · fixed in 6.12.19; From 6.13.0 · fixed in 6.13.7
References 8
git.kernel.org
- stable/c/9f28205ddb76e86cac418332e952241d85fed0dc
- stable/c/a2d1cca955ed34873e524cc2e6e885450d262f05
- stable/c/455217ac9db0cf9349b3933664355e907bb1a569
- stable/c/e8db70537878e1bb3fd83e5abcc6feefc0587828
- stable/c/01a83237644d6822bc7df2c5564fc81b0df84358
- stable/c/084819b0d8b1bd433b90142371eb9450d657f8ca
- stable/c/c32da44cc9298eaa6109e3fc2c2b4e07cc4bf11b
- stable/c/ee01b2f2d7d0010787c2343463965bbc283a497f