CVE-2026-31668seg6: separate dst_cache for input and output paths in seg6 lwtunnel
- 9.8CriticalCVSS base score
- 0.44%Exploitation in 30 daysEPSS · top 61% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
Description
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.
Timeline
ID reserved
By Linux
- 46 days later
· 46 days later
Published
- 6 months later
· 6 months later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| LinuxCNA (assigner) | 3.1 | Critical9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| NVDNVD · Modified | 3.1 | Critical9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
- EPSS (exploitation in 30 days)
- 0.44% · top 61% of all CVEs (18 Nov 2026)
- CISA SSVC
- Exploitation: none · Automatable: yes · Technical impact: total
The list uses the assigner's score when there is one, then CISA's, then NVD's: Critical 9.8.
Affected products
- affected 6c8702c60b88651072460f3f4026c7dfe2521d12 – < 1dec91d3b1cefb82635761b7812154af3ef46449
- affected 6c8702c60b88651072460f3f4026c7dfe2521d12 – < 750569d6987a0ff46317a4b86eb3907e296287bf
- affected 6c8702c60b88651072460f3f4026c7dfe2521d12 – < 57d0374d14fa667dec6952173b93e7e84486d5c9
- affected 6c8702c60b88651072460f3f4026c7dfe2521d12 – < 84d458018b147176b259347103fccb7e93abd2b1
- affected 6c8702c60b88651072460f3f4026c7dfe2521d12 – < 6305ad032b03d2ea4181b953a66e19a9a6ed053c
- affected 6c8702c60b88651072460f3f4026c7dfe2521d12 – < fb56de5d99218de49d5d43ef3a99e062ecd0f9a1
- affected 6c8702c60b88651072460f3f4026c7dfe2521d12 – < 17d87d42874f5d6c1a0ccc6d9190dfe82a9a7a6a
- affected 6c8702c60b88651072460f3f4026c7dfe2521d12 – < c3812651b522fe8437ebb7063b75ddb95b571643
- affected 4.10
- unaffected < 4.10
- unaffected 5.10.253 – ≤ 5.10.*
- unaffected 5.15.203 – ≤ 5.15.*
- unaffected 6.1.169 – ≤ 6.1.*
- unaffected 6.6.135 – ≤ 6.6.*
- unaffected 6.12.82 – ≤ 6.12.*
- unaffected 6.18.23 – ≤ 6.18.*
- unaffected 6.19.13 – ≤ 6.19.*
- unaffected 7.0 – ≤ *
References
References8
- https://git.kernel.org/stable/c/1dec91d3b1cefb82635761b7812154af3ef46449 (opens in a new tab)
- https://git.kernel.org/stable/c/750569d6987a0ff46317a4b86eb3907e296287bf (opens in a new tab)
- https://git.kernel.org/stable/c/57d0374d14fa667dec6952173b93e7e84486d5c9 (opens in a new tab)
- https://git.kernel.org/stable/c/84d458018b147176b259347103fccb7e93abd2b1 (opens in a new tab)
- https://git.kernel.org/stable/c/6305ad032b03d2ea4181b953a66e19a9a6ed053c (opens in a new tab)
- https://git.kernel.org/stable/c/fb56de5d99218de49d5d43ef3a99e062ecd0f9a1 (opens in a new tab)
- https://git.kernel.org/stable/c/17d87d42874f5d6c1a0ccc6d9190dfe82a9a7a6a (opens in a new tab)
- https://git.kernel.org/stable/c/c3812651b522fe8437ebb7063b75ddb95b571643 (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-25561 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-31668)Record last updated .