CVE-2025-21926: net: gso: fix ownership in __udp_gso_segment
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.
Security readout for executives and security teams
Plain-English summary
A Linux networking bug can leave packet metadata with inconsistent ownership. In a documented OpenVSwitch traffic path, this can trigger a kernel failure and disrupt hosts. The supplied CVSS score is 7.8 (high), but exposure depends on local access, an affected kernel, and the specific packet-processing sequence.
Executive priority
Handle through the high-priority kernel patching process, with expedited treatment for OpenVSwitch-enabled production infrastructure. The potential host disruption is serious, but the supplied evidence indicates constrained local attack conditions and does not establish active exploitation.
Technical view
In __udp_gso_segment, the skb destructor is removed while its socket reference remains. When OpenVSwitch processes a userspace action before an output action, the original skb may later reach skb_orphan and trigger a kernel BUG. Referenced stable commits correct ownership by also removing the socket reference.
Likely exposure
Most likely exposure is on Linux hosts using OpenVSwitch and UDP GSO where OVS_ACTION_ATTR_USERSPACE precedes OVS_ACTION_ATTR_OUTPUT. CVSS indicates local access, low privileges, and no user interaction. The supplied version data lacks reliable per-branch fixed boundaries, so vendor kernel and backport status must be verified.
Exploitation context
The bundle reports KEV status as false, and no supplied source establishes active exploitation or a public exploit. The documented result is a kernel BUG after skb_orphan. Although CVSS assigns high confidentiality, integrity, and availability impacts, the technical narrative directly demonstrates a crash, not confirmed data theft or code execution.
Researcher notes
The bundle repeats an introducing commit and flattens several branch versions without dependable boundary semantics. Map the referenced stable fixes to each distribution kernel before declaring exposure. The ownership defect is specifically documented, but claims beyond the demonstrated skb_orphan kernel BUG are unsupported by the supplied evidence.
Mitigation direction
Apply vendor kernel packages containing the referenced __udp_gso_segment ownership fix.
Reboot updated hosts so the corrected kernel is running.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2025-21926 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
3Timeline events
2ADP providers
12Source links
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.