Answer in brief
CVE-2026-53221 records a Critical severity (CVSS 9.8) vulnerability in ip6_vti: fix incorrect tunnel matching in vti6_tnl_lookup(). The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
Answer in brief
CVE-2026-53221 records a Critical severity (CVSS 9.8) vulnerability in ip6_vti: fix incorrect tunnel matching in vti6_tnl_lookup(). The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 9.8. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=fbe68ee87522f6eaa10f9076c0a7117e1613f2f7 <c327fa4fca31415431202e063767a7ae342e19c6 || >=fbe68ee87522f6eaa10f9076c0a7117e1613f2f7 <fc657ac0767c49839b3ef0b08dc0953ca30883f8 || >=fbe68ee87522f6eaa10f9076c0a7117e1613f2f7 <47fb3c2b4203556308e64354b3e78f2ce221d646 || >=fbe68ee87522f6eaa10f9076c0a7117e1613f2f7 <f513f308cc4bdb4530d033431592ffbc29b7fca1 || >=fbe68ee87522f6eaa10f9076c0a7117e1613f2f7 <90fd4513315ca07da99cfd8549d3e553a7160f0d || >=fbe68ee87522f6eaa10f9076c0a7117e1613f2f7 <2abfb19bbb81958714ad1d43ebeb65b30394184b || >=fbe68ee87522f6eaa10f9076c0a7117e1613f2f7 <2fc7bc087cc7085368263d9d37bfe9a0bddd6a2d || >=fbe68ee87522f6eaa10f9076c0a7117e1613f2f7 <a5c0359f5cbc51a2e2b114d6041e0f3c73f903e9 | c327fa4fca31415431202e063767a7ae342e19c6, fc657ac0767c49839b3ef0b08dc0953ca30883f8, 47fb3c2b4203556308e64354b3e78f2ce221d646, f513f308cc4bdb4530d033431592ffbc29b7fca1, 90fd4513315ca07da99cfd8549d3e553a7160f0d, 2abfb19bbb81958714ad1d43ebeb65b30394184b, 2fc7bc087cc7085368263d9d37bfe9a0bddd6a2d, a5c0359f5cbc51a2e2b114d6041e0f3c73f903e9 |
| Linux/Linuxgeneric | 3.19 | Not reported |
Published upstream
Jun 25, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Jun 25, 2026
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.
Quoted source text, attributed separately from HOL analysis.
CVSS is 9.8. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=fbe68ee87522f6eaa10f9076c0a7117e1613f2f7 <c327fa4fca31415431202e063767a7ae342e19c6 || >=fbe68ee87522f6eaa10f9076c0a7117e1613f2f7 <fc657ac0767c49839b3ef0b08dc0953ca30883f8 || >=fbe68ee87522f6eaa10f9076c0a7117e1613f2f7 <47fb3c2b4203556308e64354b3e78f2ce221d646 || >=fbe68ee87522f6eaa10f9076c0a7117e1613f2f7 <f513f308cc4bdb4530d033431592ffbc29b7fca1 || >=fbe68ee87522f6eaa10f9076c0a7117e1613f2f7 <90fd4513315ca07da99cfd8549d3e553a7160f0d || >=fbe68ee87522f6eaa10f9076c0a7117e1613f2f7 <2abfb19bbb81958714ad1d43ebeb65b30394184b || >=fbe68ee87522f6eaa10f9076c0a7117e1613f2f7 <2fc7bc087cc7085368263d9d37bfe9a0bddd6a2d || >=fbe68ee87522f6eaa10f9076c0a7117e1613f2f7 <a5c0359f5cbc51a2e2b114d6041e0f3c73f903e9 | c327fa4fca31415431202e063767a7ae342e19c6, fc657ac0767c49839b3ef0b08dc0953ca30883f8, 47fb3c2b4203556308e64354b3e78f2ce221d646, f513f308cc4bdb4530d033431592ffbc29b7fca1, 90fd4513315ca07da99cfd8549d3e553a7160f0d, 2abfb19bbb81958714ad1d43ebeb65b30394184b, 2fc7bc087cc7085368263d9d37bfe9a0bddd6a2d, a5c0359f5cbc51a2e2b114d6041e0f3c73f903e9 |
| Linux/Linuxgeneric | 3.19 | Not reported |
Published upstream
Jun 25, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Jun 25, 2026
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.
Quoted source text, attributed separately from HOL analysis.