CVE-2025-21926— net: gso: fix ownership in __udp_gso_segment
Get alerts for future matching vulnerabilitiesLog in to subscribe
I. Basic Information for CVE-2025-21926
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
net: gso: fix ownership in __udp_gso_segment
Source: NVD (National Vulnerability Database)
Vulnerability Description
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.
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存在安全漏洞，该漏洞源于__udp_gso_segment中存在所有权问题。
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
II. Public POCs for CVE-2025-21926
| # | POC Description | Source Link | Shenlong Link |
|---|
AI-Generated POCPremium
No public POC found.
Login to generate AI POCIII. Intelligence Information for CVE-2025-21926
请登录查看更多情报信息。
Same Patch Batch · Linux · 2025-04-01 · 93 CVEs total
| CVE-2025-21947 | 8.1 HIGH | ksmbd: fix type confusion via race condition when using ipc_msg_send_request |
| CVE-2025-21925 | llc: do not use skb_get() before dev_queue_xmit() | |
| CVE-2025-21932 | mm: abort vma_modify() on merge out of memory failure | |
| CVE-2025-21935 | rapidio: add check for rio_add_net() in rio_scan_alloc_net() | |
| CVE-2025-21937 | Bluetooth: Add check for mgmt_alloc_skb() in mgmt_remote_name() | |
| CVE-2025-21936 | Bluetooth: Add check for mgmt_alloc_skb() in mgmt_device_connected() | |
| CVE-2025-21939 | drm/xe/hmm: Don't dereference struct page pointers without notifier lock | |
| CVE-2025-21938 | mptcp: fix 'scheduling while atomic' in mptcp_pm_nl_append_new_local_addr | |
| CVE-2025-21934 | rapidio: fix an API misues when rio_add_net() fails | |
| CVE-2025-21928 | HID: intel-ish-hid: Fix use-after-free issue in ishtp_hid_remove() | |
| CVE-2025-21927 | nvme-tcp: fix potential memory corruption in nvme_tcp_recv_pdu() | |
| CVE-2025-21929 | HID: intel-ish-hid: Fix use-after-free issue in hid_ishtp_cl_remove() | |
| CVE-2025-21924 | net: hns3: make sure ptp clock is unregister and freed if hclge_ptp_get_cycle returns an e | |
| CVE-2025-21922 | ppp: Fix KMSAN uninit-value warning with bpf | |
| CVE-2025-21923 | HID: hid-steam: Fix use-after-free when detaching device | |
| CVE-2025-21920 | vlan: enforce underlying device type | |
| CVE-2025-21921 | net: ethtool: netlink: Allow NULL nlattrs when getting a phy_device | |
| CVE-2025-21919 | sched/fair: Fix potential memory corruption in child_cfs_rq_on_list | |
| CVE-2025-21918 | usb: typec: ucsi: Fix NULL pointer access | |
| CVE-2025-21917 | usb: renesas_usbhs: Flush the notify_hotplug_work |
Showing top 20 of 93 CVEs. View all on vendor page → →
IV. Related Vulnerabilities
Same product: Linux
- CVE-2026-43500
rxrpc: Also unshare DATA/RESPONSE packets when paged frags a - CVE-2026-43475
scsi: storvsc: Fix scheduling while atomic on PREEMPT_RT - CVE-2026-43474
fs: init flags_valid before calling vfs_fileattr_get - CVE-2026-43473
scsi: mpi3mr: Add NULL checks when resetting request and rep - CVE-2026-43472
unshare: fix unshare_fs() handling
Same vendor: Linux
- CVE-2026-43500
rxrpc: Also unshare DATA/RESPONSE packets when paged frags a - CVE-2026-43475
scsi: storvsc: Fix scheduling while atomic on PREEMPT_RT - CVE-2026-43474
fs: init flags_valid before calling vfs_fileattr_get - CVE-2026-43473
scsi: mpi3mr: Add NULL checks when resetting request and rep - CVE-2026-43472
unshare: fix unshare_fs() handling
V. Comments for CVE-2025-21926
No comments yet