CVE-2026-68477: ipvs: fix more places with wrong ipv6 transport offsets
Noroxi assessment
Priority: Monitor (action score 39/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.71% (FIRST EPSS); higher than 53.3% of all records.
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- According to CISA the attack is automatable: targets can be found by mass scanning.
- Fixed version: Linux Linux 3a9dc9b55b53d94613a587604b77d3b20024090c, 613ce63711b8d431bba90781f133c39a21684f87, 7350eb7ead172ae8024897d4b0f2e15c5318279c.
Low priority for now. Upgrade to Linux Linux 3a9dc9b55b53d94613a587604b77d3b20024090c, 613ce63711b8d431bba90781f133c39a21684f87, 7350eb7ead172ae8024897d4b0f2e15c5318279c or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Aug 15, 2026
- Updated
- Oct 19, 2026
- EPSS
- 0.7% · 53th percentile
- CWE
- CWE-20
Report tools
Action score
39
Monitor
Low priority for now.
- CVSS
- 39 / 40 · 9.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.7%
CISA SSVC decision
- Exploitation
- none
- Automatable
- yes
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · Linux
- 9.8
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 2.6.28affected
- 2a3b791e6e1169f374224d164738e9f7be703d77 and later · before 613ce63711b8d431bba90781f133c39a21684f87affected · git
- 2a3b791e6e1169f374224d164738e9f7be703d77 and later · before 95d4511d81b2b37e5d2bdde5d912e48243eae517affected · git
- 2a3b791e6e1169f374224d164738e9f7be703d77 and later · before 3a9dc9b55b53d94613a587604b77d3b20024090caffected · git
- 2a3b791e6e1169f374224d164738e9f7be703d77 and later · before a3f0d5b605cd5da5c95279969fb8cea4e55cee5baffected · git
- 2a3b791e6e1169f374224d164738e9f7be703d77 and later · before 7350eb7ead172ae8024897d4b0f2e15c5318279caffected · git
- 2a3b791e6e1169f374224d164738e9f7be703d77 and later · before d4ec18f48ce78a3bf7c999ac908691007375fe99affected · git
- 2a3b791e6e1169f374224d164738e9f7be703d77 and later · before 905d7a363ade96a19f214815361e11981142c547affected · git
- 2a3b791e6e1169f374224d164738e9f7be703d77 and later · before b3fe4cbd583895987935a9bdad01c8f9d3a02310affected · git
- before 2.6.28not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.180-1 | 6.1.180-1 |
| Debian:13 | linux | before 6.12.100-1 | 6.12.100-1 |
| Debian:14 | linux | before 7.1.5-1 | 7.1.5-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-68471Aug 15, 2026 · wifi: ieee80211: validate MLE common info length35Monitor
- ← EarlierCVE-2026-68472Aug 15, 2026 · wifi: cfg80211: validate EHT MLE before MLD ID read32Monitor
- Later →CVE-2026-68479Aug 15, 2026 · Bluetooth: btrtl: validate firmware patch bounds31Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 3a9dc9b55b53d94613a587604b77d3b20024090c | Vendor (CNA) |
| Linux Linux | 613ce63711b8d431bba90781f133c39a21684f87 | Vendor (CNA) |
| Linux Linux | 7350eb7ead172ae8024897d4b0f2e15c5318279c | Vendor (CNA) |
| Linux Linux | 905d7a363ade96a19f214815361e11981142c547 | Vendor (CNA) |
| Linux Linux | 95d4511d81b2b37e5d2bdde5d912e48243eae517 | Vendor (CNA) |
| Linux Linux | a3f0d5b605cd5da5c95279969fb8cea4e55cee5b | Vendor (CNA) |
| Linux Linux | b3fe4cbd583895987935a9bdad01c8f9d3a02310 | Vendor (CNA) |
| Linux Linux | d4ec18f48ce78a3bf7c999ac908691007375fe99 | Vendor (CNA) |
| debian:linux | 6.1.180-1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2026-720650 days apartnet: mana: Validate the packet length reported by the NIC39Monitor
- CVE-2026-681545 days apartlibceph: reject zero bucket types in crush_decode39Monitor
- CVE-2026-9999961 days apartipv4: validate checksum_start before completing checksum37Monitor
- CVE-2026-684700 days apartwifi: mac80211: validate extension-frame layout before RX35Monitor
- CVE-2026-684542 days apartKVM: s390: pci: Fix handling of AIF enable without AISB35Monitor
- CVE-2026-681995 days apartwifi: ath6kl: fix OOB access from firmware ADDBA window size35Monitor
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-20 · Improper Input ValidationCVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
- Buffer Overflow via Environment VariablesCAPEC-10likelihood: High · High
- Server Side Include (SSI) InjectionCAPEC-101likelihood: High · High
- Cross Zone ScriptingCAPEC-104likelihood: Medium · High
- Command Line Execution through SQL InjectionCAPEC-108likelihood: Low · Very High
- Object Relational Mapping InjectionCAPEC-109likelihood: Low · High
- SQL Injection through SOAP Parameter TamperingCAPEC-110likelihood: High · Very High
- Double EncodingCAPEC-120likelihood: Low · Medium
- Subverting Environment Variable ValuesCAPEC-13likelihood: High · Very High
ATT&CK techniques
- Obfuscated Files or InformationT1027
- Masquerading: Invalid Code SignatureT1036.001
- Steal Web Session CookieT1539
- Subvert Trust Controls: Code SigningT1553.002
- Impair Defenses:Impair Command History LoggingT1562.003
- Hijack Execution Flow:Dynamic Linker HijackingT1574.006
- Hijack Execution Flow:Path Interception by PATH Environment VariableT1574.007
Change log
- SSVC exploitation— → none
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (7 more)Show less
- git.kernel.org/stable/c/613ce63711b8d431bba90781f133c39a21684f87
- git.kernel.org/stable/c/7350eb7ead172ae8024897d4b0f2e15c5318279c
- git.kernel.org/stable/c/905d7a363ade96a19f214815361e11981142c547
- git.kernel.org/stable/c/95d4511d81b2b37e5d2bdde5d912e48243eae517
- git.kernel.org/stable/c/a3f0d5b605cd5da5c95279969fb8cea4e55cee5b
- git.kernel.org/stable/c/b3fe4cbd583895987935a9bdad01c8f9d3a02310
- git.kernel.org/stable/c/d4ec18f48ce78a3bf7c999ac908691007375fe99
Vendor advisories and official records. Exploit/PoC links are deliberately left out.