seg6: separate dst_cache for input and output paths in seg6 lwtunnel
28Vexday Risk Score
No sign of exploitation. No public exploitation artifact known so far.
ssvc Trackcvss 9.8epss 0.4%
exploitation probability
0.4%top 64% of all CVEs
observed exploitation
nono source reports it
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.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Affected products
Linux · LinuxReferences
https://git.kernel.org/stable/c/17d87d42874f5d6c1a0ccc6d9190dfe82a9a7a6ahttps://git.kernel.org/stable/c/1dec91d3b1cefb82635761b7812154af3ef46449https://git.kernel.org/stable/c/57d0374d14fa667dec6952173b93e7e84486d5c9https://git.kernel.org/stable/c/6305ad032b03d2ea4181b953a66e19a9a6ed053chttps://git.kernel.org/stable/c/750569d6987a0ff46317a4b86eb3907e296287bfhttps://git.kernel.org/stable/c/84d458018b147176b259347103fccb7e93abd2b1https://git.kernel.org/stable/c/c3812651b522fe8437ebb7063b75ddb95b571643https://git.kernel.org/stable/c/fb56de5d99218de49d5d43ef3a99e062ecd0f9a1