CVE-2026-53221
Last modified
CVE-2026-53221 is a critical-severity vulnerability rated 9.8/10 on the CVSS scale. 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.. EPSS estimates a 0.56% chance of exploitation in the next 30 days.
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.
Metrics
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Affected Software
| Vendor | Product | Versions | Update |
|---|---|---|---|
| Linux | Linux Kernel | >= 3.19, < 5.10.259 | — |
| Linux | Linux Kernel | >= 5.11, < 5.15.210 | — |
| Linux | Linux Kernel | >= 5.16, < 6.1.176 | — |
| Linux | Linux Kernel | >= 6.2, < 6.6.143 | — |
| Linux | Linux Kernel | >= 6.7, < 6.12.94 | — |
| Linux | Linux Kernel | >= 6.13, < 6.18.36 | — |
| Linux | Linux Kernel | >= 6.19, < 7.0.13 | — |
| Linux | Linux Kernel | 7.1 | Rc1 |
References
Timeline
- Published
- Last Modified
- Status
- Analyzed
Frequently Asked Questions
What is CVE-2026-53221?
How severe is CVE-2026-53221?
How do I fix CVE-2026-53221?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-53216In the Linux kernel, the following vulnerability has been re…9.8
- CVE-2026-53217In the Linux kernel, the following vulnerability has been re…8.6
- CVE-2026-53218In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-53219In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-5322A vulnerability has been found in AlejandroArciniegas mcp-da…7.3
- CVE-2026-53220In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-53222In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-53223In the Linux kernel, the following vulnerability has been re…7.1
- CVE-2026-53224In the Linux kernel, the following vulnerability has been re…9.1
- CVE-2026-53225In the Linux kernel, the following vulnerability has been re…9.1
- CVE-2026-53226In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-53227In the Linux kernel, the following vulnerability has been re…5.5
Are you affected by CVE-2026-53221?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
