CVE-2026-31668

CRITICALNVD 9.89.8—
EchelonGraph scoreMEDIUM confidence

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2026-04-24. NVD baseline CVSS 9.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
9.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 9.8Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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 v3
9.8
EG Score
9.8(medium)
EG Risk
49(Track)
EG Risk 49/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity98% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
37%
KEV
Not listed

Published

April 24, 2026

Last Modified

August 5, 2026

Advisory Details (8)

Auto-updated Sep 9, 2026
No patch confirmed yet.
generic

seg6: separate dst_cache for input and output paths in seg6 lwtunnel - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/c3812651b522fe8437ebb7063b75ddb95b571643
generic

seg6: separate dst_cache for input and output paths in seg6 lwtunnel - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/17d87d42874f5d6c1a0ccc6d9190dfe82a9a7a6a
generic

seg6: separate dst_cache for input and output paths in seg6 lwtunnel - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/fb56de5d99218de49d5d43ef3a99e062ecd0f9a1
generic

seg6: separate dst_cache for input and output paths in seg6 lwtunnel - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/6305ad032b03d2ea4181b953a66e19a9a6ed053c
generic

seg6: separate dst_cache for input and output paths in seg6 lwtunnel - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/84d458018b147176b259347103fccb7e93abd2b1
generic

seg6: separate dst_cache for input and output paths in seg6 lwtunnel - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/57d0374d14fa667dec6952173b93e7e84486d5c9
generic

seg6: separate dst_cache for input and output paths in seg6 lwtunnel - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/750569d6987a0ff46317a4b86eb3907e296287bf
generic

seg6: separate dst_cache for input and output paths in seg6 lwtunnel - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/1dec91d3b1cefb82635761b7812154af3ef46449

Vendor Advisories for CVE-2026-31668(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
linuxKernel @ 5.10.253—osv

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(5 across 4 ecosystems)
Debian:11(2)
PackageVulnerable rangeFixed inDependents
linux5.10.103-1 ... 5.10.92-2 (53 versions)5.10.257-1—
linux-6.16.1.106-3~deb11u1 ... 6.1.164-1~deb11u1 (16 versions)6.1.170-1~deb11u1—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 6.1.99-1 (48 versions)6.1.170-1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.85-1~bpo12+1 (17 versions)6.12.85-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 6.19~rc8-1~exp1 (127 versions)6.19.13-1—

Additional Vendor Advisories

(24)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 5× in last 7d / 34× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 419 total refreshes for this CVE.

  1. 2026-09-13 16:47 UTCEPSS rescore
  2. 2026-09-12 15:01 UTCEPSS rescore
  3. 2026-09-11 14:52 UTCEPSS rescore
  4. 2026-09-10 09:34 UTCEPSS rescore
  5. 2026-09-08 22:00 UTCEPSS rescore
  6. 2026-09-07 16:01 UTCEPSS rescore
  7. 2026-09-06 13:47 UTCEPSS rescore
  8. 2026-09-06 13:47 UTCEPSS rescore
  9. 2026-09-04 05:06 UTCEPSS rescore
  10. 2026-09-04 03:16 UTCOSV refresh
  11. 2026-09-02 14:11 UTCEPSS rescore
  12. 2026-09-01 13:53 UTCEPSS rescore
  13. 2026-09-01 04:39 UTCEPSS rescore
  14. 2026-09-01 04:39 UTCEPSS rescore
  15. 2026-08-30 19:17 UTCEPSS rescore
  16. 2026-08-30 01:22 UTCEPSS rescore
  17. 2026-08-28 21:41 UTCEPSS rescore
  18. 2026-08-27 14:25 UTCEPSS rescore
  19. 2026-08-26 14:46 UTCEPSS rescore
  20. 2026-08-25 13:49 UTCEPSS rescore
  21. 2026-08-24 14:17 UTCEPSS rescore
  22. 2026-08-23 00:19 UTCEPSS rescore
  23. 2026-08-21 23:49 UTCEPSS rescore
  24. 2026-08-20 22:55 UTCEPSS rescore
  25. 2026-08-20 22:55 UTCEPSS rescore
Show 75 more
  1. 2026-08-19 17:03 UTCEPSS rescore
  2. 2026-08-18 13:48 UTCEPSS rescore
  3. 2026-08-17 14:48 UTCEG score recompute
  4. 2026-08-17 14:48 UTCVendor advisory
  5. 2026-08-17 14:48 UTCGHSA enrichment
  6. 2026-08-17 13:47 UTCEPSS rescore
  7. 2026-08-16 14:56 UTCEPSS rescore
  8. 2026-08-16 09:42 UTCVendor advisory
  9. 2026-08-16 09:42 UTCGHSA enrichment
  10. 2026-08-16 05:46 UTCEG score recompute
  11. 2026-08-16 05:46 UTCVendor advisory
  12. 2026-08-16 05:46 UTCGHSA enrichment
  13. 2026-08-16 02:14 UTCEPSS rescore
  14. 2026-08-15 01:30 UTCEPSS rescore
  15. 2026-08-14 23:49 UTCVendor advisory
  16. 2026-08-14 23:49 UTCGHSA enrichment
  17. 2026-08-14 19:53 UTCVendor advisory
  18. 2026-08-14 19:53 UTCGHSA enrichment
  19. 2026-08-14 15:56 UTCVendor advisory
  20. 2026-08-14 15:56 UTCGHSA enrichment
  21. 2026-08-14 12:00 UTCVendor advisory
  22. 2026-08-14 12:00 UTCGHSA enrichment
  23. 2026-08-14 08:03 UTCVendor advisory
  24. 2026-08-14 08:03 UTCGHSA enrichment
  25. 2026-08-14 04:06 UTCEG score recompute
  26. 2026-08-14 04:06 UTCVendor advisory
  27. 2026-08-14 04:06 UTCGHSA enrichment
  28. 2026-08-13 22:00 UTCEPSS rescore
  29. 2026-08-13 08:30 UTCVendor advisory
  30. 2026-08-13 08:30 UTCGHSA enrichment
  31. 2026-08-13 01:40 UTCVendor advisory
  32. 2026-08-13 01:40 UTCGHSA enrichment
  33. 2026-08-12 21:44 UTCVendor advisory
  34. 2026-08-12 21:44 UTCGHSA enrichment
  35. 2026-08-12 17:47 UTCEG score recompute
  36. 2026-08-12 17:47 UTCVendor advisory
  37. 2026-08-12 17:47 UTCGHSA enrichment
  38. 2026-08-12 13:50 UTCEPSS rescore
  39. 2026-08-12 00:34 UTCVendor advisory
  40. 2026-08-12 00:34 UTCGHSA enrichment
  41. 2026-08-11 20:37 UTCVendor advisory
  42. 2026-08-11 20:37 UTCGHSA enrichment
  43. 2026-08-11 16:41 UTCEG score recompute
  44. 2026-08-11 16:41 UTCVendor advisory
  45. 2026-08-11 16:41 UTCGHSA enrichment
  46. 2026-08-11 06:05 UTCVendor advisory
  47. 2026-08-11 06:05 UTCGHSA enrichment
  48. 2026-08-11 02:08 UTCEG score recompute
  49. 2026-08-11 02:08 UTCVendor advisory
  50. 2026-08-11 02:08 UTCGHSA enrichment
  51. 2026-08-11 00:00 UTCEPSS rescore
  52. 2026-08-10 12:17 UTCVendor advisory
  53. 2026-08-10 12:17 UTCGHSA enrichment
  54. 2026-08-10 08:20 UTCVendor advisory
  55. 2026-08-10 08:20 UTCGHSA enrichment
  56. 2026-08-10 04:24 UTCVendor advisory
  57. 2026-08-10 04:24 UTCGHSA enrichment
  58. 2026-08-10 00:27 UTCVendor advisory
  59. 2026-08-10 00:27 UTCGHSA enrichment
  60. 2026-08-09 20:31 UTCVendor advisory
  61. 2026-08-09 20:31 UTCGHSA enrichment
  62. 2026-08-09 16:34 UTCEG score recompute
  63. 2026-08-09 16:34 UTCVendor advisory
  64. 2026-08-09 16:34 UTCGHSA enrichment
  65. 2026-08-09 13:46 UTCEPSS rescore
  66. 2026-08-09 12:38 UTCVendor advisory
  67. 2026-08-09 12:38 UTCGHSA enrichment
  68. 2026-08-09 07:15 UTCVendor advisory
  69. 2026-08-09 07:15 UTCGHSA enrichment
  70. 2026-08-09 03:18 UTCEG score recompute
  71. 2026-08-09 03:18 UTCVendor advisory
  72. 2026-08-09 03:18 UTCGHSA enrichment
  73. 2026-08-08 16:37 UTCEPSS rescore
  74. 2026-08-08 12:16 UTCVendor advisory
  75. 2026-08-08 12:16 UTCGHSA enrichment

Frequently asked(5)

What is CVE-2026-31668?
CVE-2026-31668 is a critical vulnerability published on April 24, 2026. 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 seg6inputcore() and seg6outputcore(). These two paths can perform the post-encap SID…
When was CVE-2026-31668 disclosed?
CVE-2026-31668 was first published in the National Vulnerability Database on April 24, 2026, with the most recent update on August 5, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-31668 actively exploited?
CVE-2026-31668 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 62.6% of all scored CVEs.
What is the CVSS score of CVE-2026-31668?
CVE-2026-31668 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2026-31668?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-31668, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-31668

Explore →

Is Your Infrastructure Affected by CVE-2026-31668?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs