CVE-2025-38572: ipv6: reject malicious packets in ipv6_gso_segment()
In the Linux kernel, the following vulnerability has been resolved:
ipv6: reject malicious packets in ipv6_gso_segment()
syzbot was able to craft a packet with very long IPv6 extension headers
leading to an overflow of skb->transport_header.
This 16bit field has a limited range.
Add skb_reset_transport_header_careful() helper and use it
from ipv6_gso_segment()
WARNING: CPU: 0 PID: 5871 at ./include/linux/skbuff.h:3032 skb_reset_transport_header include/linux/skbuff.h:3032 [inline]
WARNING: CPU: 0 PID: 5871 at ./include/linux/skbuff.h:3032 ipv6_gso_segment+0x15e2/0x21e0 net/ipv6/ip6_offload.c:151
Modules linked in:
CPU: 0 UID: 0 PID: 5871 Comm: syz-executor211 Not tainted 6.16.0-rc6-syzkaller-g7abc678e3084 #0 PREEMPT(full)
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/12/2025
RIP: 0010:skb_reset_transport_header include/linux/skbuff.h:3032 [inline]
RIP: 0010:ipv6_gso_segment+0x15e2/0x21e0 net/ipv6/ip6_offload.c:151
Call Trace:
<TASK>
skb_mac_gso_segment+0x31c/0x640 net/core/gso.c:53
nsh_gso_segment+0x54a/0xe10 net/nsh/nsh.c:110
skb_mac_gso_segment+0x31c/0x640 net/core/gso.c:53
__skb_gso_segment+0x342/0x510 net/core/gso.c:124
skb_gso_segment include/net/gso.h:83 [inline]
validate_xmit_skb+0x857/0x11b0 net/core/dev.c:3950
validate_xmit_skb_list+0x84/0x120 net/core/dev.c:4000
sch_direct_xmit+0xd3/0x4b0 net/sched/sch_generic.c:329
__dev_xmit_skb net/core/dev.c:4102 [inline]
__dev_queue_xmit+0x17b6/0x3a70 net/core/dev.c:4679
Security readout for executives and security teams
Plain-English summary
A low-privileged local attacker could submit a maliciously structured IPv6 packet that overflows a 16-bit kernel header offset during segmentation. The demonstrated result was a kernel warning; the CVSS assessment indicates potentially serious confidentiality, integrity, and availability consequences. No user interaction is required.
Executive priority
Prioritize remediation in the normal high-severity patch cycle, accelerating internet infrastructure and shared compute environments with untrusted local workloads. This is not supported as an emergency remote-exploitation event, but potential kernel-level impact warrants prompt inventory, vendor verification, updating, and rebooting.
Technical view
Excessively long IPv6 extension headers can overflow skb->transport_header in ipv6_gso_segment(). The kernel fix adds a careful transport-header reset that rejects unsafe offsets. The supplied record scores this CVSS 3.1 at 7.8 with local access and low privileges required.
Likely exposure
Exposure applies to affected Linux kernels lacking the relevant stable fix or distribution backport. Risk is greatest where untrusted local users or workloads can reach the IPv6 packet-segmentation path. The supplied version data is irregular, so assess vendor kernels by advisory and backported commit status, not version strings alone.
Exploitation context
The issue was reproduced by syzbot using a crafted packet. The supplied record is not in KEV and provides no evidence of active exploitation or a public weaponized exploit. Local access and low privileges are reflected in the supplied CVSS vector; remotely reachable exploitation is not established.
Researcher notes
The demonstrated evidence shows an offset overflow and warning in ipv6_gso_segment(), not confirmed real-world compromise. No CWE is supplied. The affected-version list contains ambiguous entries, including “0” and “6.17”; authoritative distribution advisories and stable-commit backport checks are therefore essential for exposure decisions.
Mitigation direction
Install the vendor-supported kernel update containing the applicable stable fix.
Reboot into the updated kernel; installing a package alone may leave the vulnerable kernel running.
If no update is available, obtain mitigation guidance from the Linux distribution vendor.
Prioritize multi-user systems and hosts running untrusted workloads.
Validation and detection
Record the running kernel version, build, and distribution package release.
Check the distribution advisory for a backport of the referenced kernel fix.
Confirm the applicable stable commit exists in custom kernel source or build metadata.
After rebooting, verify the running kernel matches the remediated package.
Review kernel logs for related warnings, without treating absence as proof of safety.
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-38572 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
1ADP 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.