seg6: separate dst_cache for input and output paths in seg6 lwtunnel
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 6c8702c60b88651072460f3f4026c7dfe2521d12 · < fb56de5d99218de49d5d43ef3a99e062ecd0f9a1| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
seg6: separate dst_cache for input and output paths in seg6 lwtunnel
The seg6 lwtunnel uses a single dst_cache per encap route, shared between seg6_input_core() and seg6_output_core(). These two paths can perform the post-encap SID lookup in different routing contexts (e.g., ip rules matching on the ingress interface, or VRF table separation). Whichever path runs first populates the cache, and the other reuses it blindly, bypassing its own lookup.
Fix this by splitting the cache into cache_input and cache_output, so each path maintains its own cached dst independently.
From the CVE record · Linux
The Linux kernel’s seg6 lwtunnel shares a destination cache between input and output paths. When those paths use different routing contexts, the path that runs second can reuse the first path’s cached route and bypass its own lookup. The input does not establish attacker access, authentication, or user-interaction requirements.
Teams running Linux kernels with seg6 lwtunnel should check their versions; affected versions are not specified.