CyberSecBulletin
CVE-2026-68477NVD status: Received

In the Linux kernel, the following vulnerability has been resolved: ipvs: fix more places with…

Published Updated By the CyberSecBulletin desk

CVE-2026-68477 is a critical-severity improper input validation vulnerability in Linux, with a CVSS 3.1 base score of 9.8 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. The record lists versions 613ce63711b8d431bba90781f133c39a21684f87, 95d4511d81b2b37e5d2bdde5d912e48243eae517, 3a9dc9b55b53d94613a587604b77d3b20024090c as the first without the flaw, so updating Linux to one of those releases or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.71% chance of exploitation within 30 days, higher than 54% of scored CVEs.

Patch this week

Critical severity: a successful attack would have severe impact.

What to do

  1. Update Linux to 613ce63711b8d431bba90781f133c39a21684f87 or 95d4511d81b2b37e5d2bdde5d912e48243eae517 or 3a9dc9b55b53d94613a587604b77d3b20024090c or a3f0d5b605cd5da5c95279969fb8cea4e55cee5b, whichever matches your release line, or a later version.
  2. Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.

Affected products and versions

VendorProductAffected versionsFixed in
LinuxLinux2a3b791e6e1169f374224d164738e9f7be703d77 up to, but not including, 613ce63711b8d431bba90781f133c39a21684f87; 2a3b791e6e1169f374224d164738e9f7be703d77 up to, but not including, 95d4511d81b2b37e5d2bdde5d912e48243eae517; 2a3b791e6e1169f374224d164738e9f7be703d77 up to, but not including, 3a9dc9b55b53d94613a587604b77d3b20024090c; 2a3b791e6e1169f374224d164738e9f7be703d77 up to, but not including, a3f0d5b605cd5da5c95279969fb8cea4e55cee5b; 2a3b791e6e1169f374224d164738e9f7be703d77 up to, but not including, 7350eb7ead172ae8024897d4b0f2e15c5318279c; 2a3b791e6e1169f374224d164738e9f7be703d77 up to, but not including, d4ec18f48ce78a3bf7c999ac908691007375fe99; 2a3b791e6e1169f374224d164738e9f7be703d77 up to, but not including, 905d7a363ade96a19f214815361e11981142c547; 2a3b791e6e1169f374224d164738e9f7be703d77 up to, but not including, b3fe4cbd583895987935a9bdad01c8f9d3a02310; and 1 more ranges613ce63711b8d431bba90781f133c39a21684f87, 95d4511d81b2b37e5d2bdde5d912e48243eae517, 3a9dc9b55b53d94613a587604b77d3b20024090c, a3f0d5b605cd5da5c95279969fb8cea4e55cee5b, 7350eb7ead172ae8024897d4b0f2e15c5318279c, d4ec18f48ce78a3bf7c999ac908691007375fe99

Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.

How the severity score breaks down

Attack vector
NetworkCan be exploited remotely over a network, including the internet.
Attack complexity
LowNo special conditions are needed; the attack works reliably.
Privileges required
NoneNo account or login is needed.
User interaction
NoneNo action by a victim is required.
Scope
UnchangedImpact stays within the vulnerable component.
Confidentiality
HighAll data handled by the component can be read.
Integrity
HighData or code can be modified at will.
Availability
HighThe component can be taken down completely.

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H. Scored by CNA.

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.

Source: the CVE record as published by its numbering authority, via NVD and CVE.org.

The underlying weakness: Improper Input Validation

The product receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required to process the data safely and correctly.

How developers prevent this class of flaw

  • Consider using language-theoretic security (LangSec) techniques that characterize inputs using a formal language and build recognizers for that language. This effectively requires parsing to be a distinct layer that effectively enforces a boundary between raw input and internal data representations, instead of allowing parser code to be scattered throughout the program, where it could be subject to errors or inconsistencies that create weaknesses.
  • Use an input validation framework such as Struts or the OWASP ESAPI Validation API. Note that using a framework does not automatically address all input validation problems; be mindful of weaknesses that could arise from misusing the framework itself (CWE-1173).
  • Understand all the potential areas where untrusted inputs can enter the product, including but not limited to: parameters or arguments, cookies, anything read from the network, environment variables, reverse DNS lookups, query results, request headers, URL components, e-mail, files, filenames, databases, and any external systems that provide data to the application. Remember that such inputs may be obtained indirectly through API calls.

More Improper Input Validation vulnerabilities (CWE-20)

Timeline

  1. CVE record published.
  2. CISA published its SSVC assessment (exploitation: none, automatable: yes, technical impact: total).
  3. Record last changed materially (score, affected products, status or references).

References

Recent Improper Input Validation vulnerabilities

Spotted an error? Tell us.