Remote memory corruption via wrong IPv6 offsets
Published Aug 15, 2026 · Updated Aug 15, 2026
Improper IPv6 packet handling in the Linux kernel IPVS component allows remote attackers to corrupt packets via crafted extension headers. The TCP application path uses an IPv4 header length for IPv6 traffic, while ip_vs_out_icmp_v6() passes a fixed IPv6 header size instead of the parsed offset to checksum and NAT logic. Exposure requires an IPVS virtual service processing IPv6 packets with extension headers; consequences include information disclosure, packet-data corruption, connection interruption, or a kernel crash.
Summary
What happened
Improper IPv6 packet handling in the Linux kernel IPVS component allows remote attackers to corrupt packets via crafted extension headers. The TCP application path uses an IPv4 header length for IPv6 traffic, while ip_vs_out_icmp_v6() passes a fixed IPv6 header size instead of the parsed offset to checksum and NAT logic. Exposure requires an IPVS virtual service processing IPv6 packets with extension headers; consequences include information disclosure, packet-data corruption, connection interruption, or a kernel crash.
The record
- CVE
- CVE-2026-68477
- Published
- Aug 15, 2026
- Updated
- Aug 15, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-354, T1499
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 15, 2026CVE publishedPublication date reported by the CVE source.
- Aug 15, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=2.6.28
- Affected versionversion=2a3b791e6e1169f374224d164738e9f7be703d77 <3a9dc9b55b53d94613a587604b77d3b20024090c
- Affected versionversion=2a3b791e6e1169f374224d164738e9f7be703d77 <613ce63711b8d431bba90781f133c39a21684f87
- Affected versionversion=2a3b791e6e1169f374224d164738e9f7be703d77 <7350eb7ead172ae8024897d4b0f2e15c5318279c
- Affected versionversion=2a3b791e6e1169f374224d164738e9f7be703d77 <905d7a363ade96a19f214815361e11981142c547
- Affected versionversion=2a3b791e6e1169f374224d164738e9f7be703d77 <95d4511d81b2b37e5d2bdde5d912e48243eae517
- Affected versionversion=2a3b791e6e1169f374224d164738e9f7be703d77 <a3f0d5b605cd5da5c95279969fb8cea4e55cee5b
- Affected versionversion=2a3b791e6e1169f374224d164738e9f7be703d77 <b3fe4cbd583895987935a9bdad01c8f9d3a02310
- Affected versionversion=2a3b791e6e1169f374224d164738e9f7be703d77 <d4ec18f48ce78a3bf7c999ac908691007375fe99
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo