CVE-2026-31668
Linux Kernel 4.10.1 – 5.10.253
Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HCVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). EPSS scores by FIRST (EPSS SIG), generated by Empirical Security. Risk Priority is our own derived reading, not an NVD score.
Summary
CVE-2026-31668 is a critical-severity Incomplete Cleanup (CWE-459) vulnerability in Linux Kernel. Its CVSS base score is 9.8 (Critical).
Operationally, exploitation aligns with the MITRE ATT&CK technique Credentials In Files (T1552.001); ranked at the 38th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2026-31668 affects the Linux kernel's seg6 lwtunnel implementation, where a single dst_cache is shared between the input path (seg6_input_core()) and output path (seg6_output_core()). These paths perform post-encap SID lookups in different routing contexts, such as ip rules matching on the ingress interface or VRF table separation. The first path to execute populates the cache, while the second reuses it blindly, bypassing its own lookup. The vulnerability carries a CVSS score of 9.8 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H).
Remote unauthenticated attackers can exploit this vulnerability over the network with low complexity and no user interaction. By triggering the shared cache reuse across differing routing contexts, attackers may bypass intended routing decisions, potentially leading to high impacts on confidentiality, integrity, and availability through disrupted or misdirected traffic handling in seg6 environments.
Mitigation requires updating to patched Linux kernel versions via the stable repository commits referenced in the advisory, including https://git.kernel.org/stable/c/17d87d42874f5d6c1a0ccc6d9190dfe82a9a7a6a, https://git.kernel.org/stable/c/1dec91d3b1cefb82635761b7812154af3ef46449, https://git.kernel.org/stable/c/57d0374d14fa667dec6952173b93e7e84486d5c9, https://git.kernel.org/stable/c/6305ad032b03d2ea4181b953a66e19a9a6ed053c, and https://git.kernel.org/stable/c/750569d6987a0ff46317a4b86eb3907e296287bf, which separate the cache into cache_input and cache_output for independent lookups per path.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-25561
Vulnerability Data
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…
more
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.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V6.4.1
Likely Mitigating Controls AI
Per-CVE control mapping for this CVE has not run yet; the list below is derived from the weakness types (CWEs) cited in the NVD entry.
Mandates complete sanitization during cleanup so that shared resources (memory, caches, buffers) do not retain data across subjects.
Operational retention schedules mandate complete cleanup of temporary or residual sensitive data after use.
Termination of the non-persistent artifact guarantees cleanup of temporary state, directly countering incomplete cleanup weaknesses.
Fail-safe procedures can explicitly require cleanup of temporary state, resources, or privileges on failure to avoid leaving the system in an inconsistent state.
The explicit delete step when information is no longer needed implements the cleanup that this weakness omits.
Enforces complete cleanup and sanitization steps during disposal, closing gaps that leave data remnants on retired components.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Secure-development practices and coding standards normally require proper resource release and cleanup.
Life-cycle management encompasses disposal of temporary resources but does not specifically target runtime cleanup bugs.
Explicitly calls for removing sensitive data after use, directly addressing one class of incomplete cleanup.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Secure-coding rules can mandate explicit cleanup of temporary resources, but do not guarantee it.
Change-management processes may require cleanup verification, but the control itself does not address the weakness.