CVE-2026-68477
Linux kernel vulnerability
- Published15 Aug 2026
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.
CVSS 3.1 breakdown
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HRemediation
No fixed version is recorded in the NVD data. Check the vendor advisory for the latest guidance.
References
- https://git.kernel.org/stable/c/3a9dc9b55b53d94613a587604b77d3b20024090c
- https://git.kernel.org/stable/c/613ce63711b8d431bba90781f133c39a21684f87
- https://git.kernel.org/stable/c/7350eb7ead172ae8024897d4b0f2e15c5318279c
- https://git.kernel.org/stable/c/905d7a363ade96a19f214815361e11981142c547
- https://git.kernel.org/stable/c/95d4511d81b2b37e5d2bdde5d912e48243eae517
- https://git.kernel.org/stable/c/a3f0d5b605cd5da5c95279969fb8cea4e55cee5b
- https://git.kernel.org/stable/c/b3fe4cbd583895987935a9bdad01c8f9d3a02310
- https://git.kernel.org/stable/c/d4ec18f48ce78a3bf7c999ac908691007375fe99
Frequently asked
Is CVE-2026-68477 being actively exploited?
CVE-2026-68477 is not in the CISA KEV catalog. Its EPSS exploit probability is 0.76%.
How severe is CVE-2026-68477?
CVE-2026-68477 has a CVSS 3.1 base score of 9.8, rated critical. EPSS estimates a 0.76% probability of exploitation.
How do I fix CVE-2026-68477?
Apply the vendor's patch or advisory guidance, then verify no affected versions remain across your devices.
How Secuno handles this
Secuno correlates vulnerabilities like CVE-2026-68477 against the real software inventory on every managed device, as each hourly inventory arrives. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.
Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.