ip6_vti: fix incorrect tunnel matching in vti6_tnl_lookup()
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ fbe68ee87522f6eaa10f9076c0a7117e1613f2f7 · < 2abfb19bbb81958714ad1d43ebeb65b30394184b| No fix yet |
| Linux Linux |
|
|
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.
From the CVE record · Linux
The Linux kernel's ip6_vti tunnel lookup can select the wrong wildcard tunnel when an exact match fails and tunnels collide in its hash table. A network packet can trigger the incorrect match; the input does not specify authentication requirements or user interaction.
Engineers running Linux kernels that include the affected ip6_vti lookup code should check their versions against the vendor advisory.