VDB

CVE-2025-21926

CVE-2025-21926 PUBLISHED CVSS 7.8 HIGH

net: gso: fix ownership in __udp_gso_segment

Reported by linux · Published April 1, 2025

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.

Fixed versions

Upgrade to a fixed version or later. Language registries are listed first, then Linux distributions, then vendor products.

PackageEcosystemFixed in
perfAmazon Linux6.1.131-143.221.amzn2023
LinuxLinuxee01b2f2d7d0010787c2343463965bbc283a497f, e8db70537878e1bb3fd83e5abcc6feefc0587828, c32da44cc9298eaa6109e3fc2c2b4e07cc4bf11b, a2d1cca955ed34873e524cc2e6e885450d262f05, 9f28205ddb76e86cac418332e952241d85fed0dc, 455217ac9db0cf9349b3933664355e907bb1a569, 4.18, 084819b0d8b1bd433b90142371eb9450d657f8ca, 01a83237644d6822bc7df2c5564fc81b0df84358

Risk scores

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

Affected products

VendorProductVersions
LinuxLinuxad405857b174ed31a97982bb129c320d03321cf5, ad405857b174ed31a97982bb129c320d03321cf5, ad405857b174ed31a97982bb129c320d03321cf5
LinuxLinux4.18, 0, 5.4.291
amazon:2023perf0
LinuxLinux*, *, *
amazon:2023kernel-tools0
amazon:2023kernel-livepatch-6.1.131-143.2210
amazon:2023kernel0
amazon:2023kernel-tools-devel0
SiemensSIMATIC S7-1500 CPU 1518-4 PN/DP MFP3.1.7, 3.1.6
amazon:2023kernel-modules-extra0
amazon:2023perf6.120
amazon:2023kernel6.120
amazon:2023kernel-libbpf-static0
amazon:2023kernel-libbpf0
amazon:2023python3-perf0
amazon:2023kernel-modules-extra-common0
amazon:2023kernel6.12-modules-extra0
amazon:2023kernel-livepatch-6.12.22-27.960
amazon:2023python3-perf6.120
amazon:2023kernel-headers0

…and 6 more

Timeline

  • Apr 1, 2025 CVE Published
  • Apr 2, 2025 EPSS Score (30 in total, the first dated here)
  • May 9, 2025 Coalition ESS Score (15 in total, the first dated here)
  • Dec 22, 2025 Security Advisory (264 in total, the first dated here)
  • Apr 29, 2026 Distribution Patch (238 in total, the first dated here)
  • Oct 13, 2026 CVE Updated

Query this with the API

The same record, from the CLI:

vulnetix vdb vuln CVE-2025-21926
vulnetix vdb fixes CVE-2025-21926

Or with curl, using the org id and key from your account page:

curl -s -H "Authorization: ApiKey ${VULNETIX_ORG_ID}:${VULNETIX_API_KEY}" \
  "https://api.vdb.vulnetix.com/v2/vuln/CVE-2025-21926/fixes/registry"

The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart

Look up in the Resolve Platform →
$ Lookup Community · 50/day Open Lookup ›