Skip to main content
VulnerabilityPublished Updated

CVE-2026-68477: Linux kernel · Improper Input Validation

Affects Linux kernelSource CVE Database V5

0

Not known to be exploited · CVSS 9.8 Critical · fixed in d4ec18f48ce78a3bf7c999ac908691007375fe99 : patch Linux kernel as a priority.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.7% chance of exploitation in 30 days – higher than 53% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CISA SSVC
Exploitation
No evidence of active exploitation and no public proof of concept
Automatable
Attackers can reliably automate steps 1–4 of the kill chain
Technical impact
Total control over the software or total information disclosure

CISA SSVC assessment, 2026-10-16.

Patch
Available – fixed in d4ec18f48ce78a3bf7c999ac908691007375fe99, b3fe4cbd583895987935a9bdad01c8f9d3a02310, a3f0d5b605cd5da5c95279969fb8cea4e55cee5b +5
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 15 Aug 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ 2a3b791e6e1169f374224d164738e9f7be703d77, < d4ec18f48ce78a3bf7c999ac908691007375fe99
Fixed in
  • d4ec18f48ce78a3bf7c999ac908691007375fe99
LinuxLinuxAffected
  • ≥ 2a3b791e6e1169f374224d164738e9f7be703d77, < b3fe4cbd583895987935a9bdad01c8f9d3a02310
Fixed in
  • b3fe4cbd583895987935a9bdad01c8f9d3a02310
LinuxLinuxAffected
  • ≥ 2a3b791e6e1169f374224d164738e9f7be703d77, < a3f0d5b605cd5da5c95279969fb8cea4e55cee5b
Fixed in
  • a3f0d5b605cd5da5c95279969fb8cea4e55cee5b
LinuxLinuxAffected
  • ≥ 2a3b791e6e1169f374224d164738e9f7be703d77, < 7350eb7ead172ae8024897d4b0f2e15c5318279c
Fixed in
  • 7350eb7ead172ae8024897d4b0f2e15c5318279c
LinuxLinuxAffected
  • ≥ 2a3b791e6e1169f374224d164738e9f7be703d77, < 905d7a363ade96a19f214815361e11981142c547
Fixed in
  • 905d7a363ade96a19f214815361e11981142c547
LinuxLinuxAffected
  • ≥ 2a3b791e6e1169f374224d164738e9f7be703d77, < 613ce63711b8d431bba90781f133c39a21684f87
Fixed in
  • 613ce63711b8d431bba90781f133c39a21684f87

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.

References

Community reviews

Loading reviews…