ipvs: fix more places with wrong ipv6 transport offsets
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 2a3b791e6e1169f374224d164738e9f7be703d77 · < d4ec18f48ce78a3bf7c999ac908691007375fe99| No fix yet |
| Linux Linux |
|
|
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.
From the CVE record · Linux
The Linux kernel’s IPVS code uses incorrect IPv6 transport offsets in some paths. This can cause problems for applications over IPv6 and incorrect ICMPv6 checksum checks when packets have extension headers. The input does not establish what an attacker could accomplish or whether authentication or user interaction is required.
Engineers running the Linux kernel with IPVS should check their deployments; affected versions are not specified.