CVE-2025-38572: ipv6: reject malicious packets in ipv6_gso_segment()
Telemetry drift only. No threshold crossed and no authority ruling changed.
CVE record, CISA KEV and EPSS as of 2026-10-18.
CVEs like this one computed, by meaning
What to do now held facts and links
- Upgrade to the fixed version for your release line, or later: kernel 5.10.241; kernel 5.15.190; kernel 5.4.297; kernel 6.1.148; kernel 6.12.42; kernel 6.15.10 upper bounds of the CVE record's affected ranges
- Record your decision, dated and frozen with today's evidence: patch by a date · mitigated by a compensating control · deferred · accepted the risk · not affected
- Check your version against the ranges this record publishes.
What it is stated by the CNA
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…
- weakness
- Not named by the CNA.
- affected
- Linux
- published ranges
- linux kernel >= 3.8 < 5.4.297; linux kernel >= 5.5 < 5.10.241; linux kernel >= 5.11 < 5.15.190; linux kernel >= 5.16 < 6.1.148; and 5 more on the CVE page
- first unaffected version, by branch
- kernel 5.10.241; kernel 5.15.190; kernel 5.4.297; kernel 6.1.148; kernel 6.12.42; kernel 6.15.10
- fixed by package (from OSV advisories)
- Kernel (Linux): 5.4.297; 5.15.190; 6.1.148; 5.10.241; 6.15.10; 6.16.1; 6.6.102; 6.12.42 CVE-2025-38572
- severity
- 7.8 CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- assigned by
- Linux
- published
- 2025-08-19
check us git.kernel.org git.kernel.org git.kernel.org git.kernel.org
Exploit code held, dated
- exploit code
- None held in the PoC-in-GitHub feed. A public repository changes this brief.
What moved held, dated
| date | EPSS | event |
|---|---|---|
| 20 Aug 2025 | 0.00024 | |
| 25 Aug 2025 | 0.00032 | |
| 29 Aug 2025 | 0.00043 | |
| 20 Sep 2025 | 0.00047 | |
| 15 Jun 2026 | 0.0018 | scoring model v2026.06.15 |
| 12 Aug 2026 | 0.00192 | |
| 28 Aug 2026 | 0.00179 | |
| 8 Sep 2026 | 0.00183 | |
| 28 Sep 2026 | 0.00184 |
22 observations held. A step marked with a scoring model moved because the measurement was replaced, not because the vulnerability changed.
Outside the record researched, cited
This section reads the record's references and adds cited findings from outside it. It needs an account. Everything above is held facts and is complete without it.
What would change this brief held, dated
- CISA KEV
- Not listed in the catalogue we hold. A listing changes this brief.
- exploit probability
- 0.00 on 2026-09-28 (FIRST's EPSS, a probability and not evidence of exploitation). Next band line: 10% (0.10). Crossing a line changes this brief.
- fix
- Held: kernel 5.10.241; kernel 5.15.190; kernel 5.4.297; kernel 6.1.148; kernel 6.12.42; kernel 6.15.10. A newer fix from the CNA or OSV changes this brief.
How to check this
Every value above is held with two dates: when it was true upstream (as_of) and when we recorded it (tx_from). Re-derive the exploit probability as it stood on any date:
SELECT value, source, source_version, as_of, tx_from
FROM volatile_valid_as_of('CVE-2025-38572', '2026-11-01T23:59:59.999999Z', now());