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

> Incorrect IPv6 transport offsets in the Linux kernel IPVS module can cause issues with IPv6 applications, potentially leading to service disruption.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 15 Aug 2026
- **Updated:** 19 Oct 2026
- **Also known as:** BELL-CVE-2026-68477, DEBIAN-CVE-2026-68477, GHSA-g55r-28w7-4fjw, UBUNTU-CVE-2026-68477

## What is CVE-2026-68477?

CVE-2026-68477 is a critical vulnerability in Linux, published on 15 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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.

Weakness: CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2026-68477?


## How do I fix CVE-2026-68477?

Apply the vendor's patch.

## Is CVE-2026-68477 being exploited?

There is no known exploitation of CVE-2026-68477 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-68477 and fix it if it is affected.

What it is: CVE-2026-68477 is a critical vulnerability in Linux, published on 15 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-68477 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-68477/ (Markdown: https://insights.sbomify.com/CVE-2026-68477/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-68477
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-68477
- OSV: https://osv.dev/vulnerability/CVE-2026-68477

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-68477/
Summaries are generated and may contain mistakes; the official description above is the record.