CVE-2026-53221: Linux kernel · ip6_vti: fix incorrect tunnel matching in vti6_tnl_lookup()
Affects Linux kernelSource CVE Database V5
Not known to be exploited · CVSS 9.8 Critical · fixed in fc657ac0767c49839b3ef0b08dc0953ca30883f8 : patch Linux kernel as a priority.
Data as of 26 Oct 2026, 17:30 UTC
- EPSS
- 0.5% chance of exploitation in 30 days – higher than 47% 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 fc657ac0767c49839b3ef0b08dc0953ca30883f8, f513f308cc4bdb4530d033431592ffbc29b7fca1, c327fa4fca31415431202e063767a7ae342e19c6 +5
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 25 Jun 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
Description
In the Linux kernel, the following vulnerability has been resolved: ip6_vti: fix incorrect tunnel matching in vti6_tnl_lookup() In vti6_tnl_lookup(), when an exact match for a tunnel fails, the code falls back to searching for wildcard tunnels: - Tunnels matching the packet's local address, with any remote address wildcard remote). - Tunnels matching the packet's remote address, with any local address (wildcard local). However, vti6 stores all these different types of tunnels in the same hash table (ip6n->tnls_r_l) prone to hash collisions. The bug is that the fallback search loops in vti6_tnl_lookup() were missing checks to ensure that the candidate tunnel actually has a wildcard address.
References
- git.kernel.org/stable/c/c327fa4fca31415431202e063767a7ae342e19c6 (opens in a new tab)
- git.kernel.org/stable/c/fc657ac0767c49839b3ef0b08dc0953ca30883f8 (opens in a new tab)
- git.kernel.org/stable/c/47fb3c2b4203556308e64354b3e78f2ce221d646 (opens in a new tab)
- git.kernel.org/stable/c/f513f308cc4bdb4530d033431592ffbc29b7fca1 (opens in a new tab)
- git.kernel.org/stable/c/90fd4513315ca07da99cfd8549d3e553a7160f0d (opens in a new tab)
- git.kernel.org/stable/c/2abfb19bbb81958714ad1d43ebeb65b30394184b (opens in a new tab)
- git.kernel.org/stable/c/2fc7bc087cc7085368263d9d37bfe9a0bddd6a2d (opens in a new tab)
- git.kernel.org/stable/c/a5c0359f5cbc51a2e2b114d6041e0f3c73f903e9 (opens in a new tab)
- cert-portal.siemens.com/productcert/html/ssa-784472.html (opens in a new tab)