LiveActive security incident?Get immediate response
CVE Record

CVE-2025-38124: net: fix udp gso skb_segment after pull from frag_list

In the Linux kernel, the following vulnerability has been resolved: net: fix udp gso skb_segment after pull from frag_list Commit a1e40ac5b5e9 ("net: gso: fix udp gso fraglist segmentation after pull from frag_list") detected invalid geometry in frag_list skbs and redirects them from skb_segment_list to more robust skb_segment. But some packets with modified geometry can also hit bugs in that code. We don't know how many such cases exist. Addressing each one by one also requires touching the complex skb_segment code, which risks introducing bugs for other types of skbs. Instead, linearize all these packets that fail the basic invariants on gso fraglist skbs. That is more robust. If only part of the fraglist payload is pulled into head_skb, it will always cause exception when splitting skbs by skb_segment. For detailed call stack information, see below. Valid SKB_GSO_FRAGLIST skbs - consist of two or more segments - the head_skb holds the protocol headers plus first gso_size - one or more frag_list skbs hold exactly one segment - all but the last must be gso_size Optional datapath hooks such as NAT and BPF (bpf_skb_pull_data) can modify fraglist skbs, breaking these invariants. In extreme cases they pull one part of data into skb linear. For UDP, this causes three payloads with lengths of (11,11,10) bytes were pulled tail to become (12,10,10) bytes. The skbs no longer meets the above SKB_GSO_FRAGLIST conditions because payload was pulled into head_skb, it needs to be linearized before pass to regular skb_segment. skb_segment+0xcd0/0xd14 __udp_gso_segment+0x334/0x5f4 udp4_ufo_fragment+0x118/0x15c inet_gso_segment+0x164/0x338 skb_mac_gso_segment+0xc4/0x13c __skb_gso_segment+0xc4/0x124 validate_xmit_skb+0x9c/0x2c0 validate_xmit_skb_list+0x4c/0x80 sch_direct_xmit+0x70/0x404 __dev_queue_xmit+0x64c/0xe5c neigh_resolve_output+0x178/0x1c4 ip_finish_output2+0x37c/0x47c __ip_finish_output+0x194/0x240 ip_finish_output+0x20/0xf4 ip_output+0x100/0x1a0 NF_HOOK+0xc4/0x16c ip_forward+0x314/0x32c ip_rcv+0x90/0x118 __netif_receive_skb+0x74/0x124 process_backlog+0xe8/0x1a4 __napi_poll+0x5c/0x1f8 net_rx_action+0x154/0x314 handle_softirqs+0x154/0x4b8 [118.376811] [C201134] rxq0_pus: [name:bug&]kernel BUG at net/core/skbuff.c:4278! [118.376829] [C201134] rxq0_pus: [name:traps&]Internal error: Oops - BUG: 00000000f2000800 [#1] PREEMPT SMP [118.470774] [C201134] rxq0_pus: [name:mrdump&]Kernel Offset: 0x178cc00000 from 0xffffffc008000000 [118.470810] [C201134] rxq0_pus: [name:mrdump&]PHYS_OFFSET: 0x40000000 [118.470827] [C201134] rxq0_pus: [name:mrdump&]pstate: 60400005 (nZCv daif +PAN -UAO) [118.470848] [C201134] rxq0_pus: [name:mrdump&]pc : [0xffffffd79598aefc] skb_segment+0xcd0/0xd14 [118.470900] [C201134] rxq0_pus: [name:mrdump&]lr : [0xffffffd79598a5e8] skb_segment+0x3bc/0xd14 [118.470928] [C201134] rxq0_pus: [name:mrdump&]sp : ffffffc008013770

HighCVSS 7.5Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

A Linux networking flaw can crash the kernel while segmenting specially altered UDP traffic, causing service disruption or a system outage. The supplied assessment rates it CVSS 7.5 because exploitation may be remote, requires no privileges or user action, and primarily affects availability.

Executive priority

Treat as a high-priority availability issue for exposed Linux networking infrastructure, especially gateways and appliances. Patch through normal emergency maintenance where an affected build and relevant datapath are confirmed. Broader crisis action is not supported because the supplied sources show no active exploitation.

Technical view

UDP GSO frag-list packets can violate expected segment geometry after datapath processing pulls payload into the head buffer. NAT or BPF hooks are cited as possible modifiers. Passing the malformed layout to skb_segment can trigger a kernel BUG/Oops. The referenced kernel changes linearize packets failing basic frag-list invariants before segmentation.

Likely exposure

Exposure is most plausible on affected Linux kernels processing UDP GSO frag-list traffic, particularly where NAT or BPF datapath hooks modify packet buffers. The supplied version data identifies affected releases and commits but is not a complete distribution-specific inventory; administrators should confirm backports with their Linux vendor.

Exploitation context

The CVSS vector describes network-reachable, low-complexity, unauthenticated denial of service without user interaction. However, the bundle marks KEV false and provides no evidence of active exploitation or a public exploit. Practical reachability may depend on networking configuration and whether packet processing produces the invalid geometry.

Researcher notes

The failure arises when partial frag-list payload pulling changes segment lengths and violates SKB_GSO_FRAGLIST invariants. The documented outcome is a kernel BUG/Oops in skb_segment. Evidence supports denial of service, not confidentiality or integrity impact. The description acknowledges that the full number of problematic packet geometries is unknown.

Mitigation direction

  • Upgrade to a vendor-supported kernel containing the applicable referenced fix.
  • Check distribution or appliance advisories for backported patches and exact fixed package versions.
  • Prioritize internet-facing routers, gateways, hosts, and appliances using Linux NAT or BPF networking.
  • Follow vendor guidance if immediate kernel replacement is operationally constrained.

Validation and detection

  • Record running kernel and package versions across Linux hosts and appliances.
  • Compare each build with the CVE record and distribution-specific backport advisories.
  • Identify systems processing UDP traffic through NAT, BPF, or GSO frag-list paths.
  • Review kernel logs for BUG or Oops events referencing skb_segment and UDP GSO segmentation.
  • After updating, verify the running kernel contains the vendor-provided correction.
Prepared
Confidence
high
Sources
9

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-38124 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.5 (3.1)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

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
8Source 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.

ScoreVersionSeverityVectorExploitImpactSource
7.5CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H3.93.6Linux

Vulnerability scoring details

Base CVSS 3.1 score

7.5High
CVSS 3.1 vector shape for CVE-2025-38124Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CVECVE Program Container
siemens-SADPADP container
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux080e6c9a3908de193a48f646c5ce1bfb15676ffc, af3122f5fdc0d00581d6e598a668df6bf54c9daa, a1e40ac5b5e9077fe1f7ae0eb88034db0f9ae1ab, a1e40ac5b5e9077fe1f7ae0eb88034db0f9ae1ab, a1e40ac5b5e9077fe1f7ae0eb88034db0f9ae1ab, 33e28acf42ee863f332a958bfc2f1a284a3659df, 3cd00d2e3655fad3bda96dc1ebf17b6495f86fea, 6.1.113, 6.6.55, 6.10.14, 6.11.3unaffected
LinuxLinux6.12, 0, 6.1.142, 6.6.94, 6.12.34, 6.15.3, 6.16affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.