cve.bz

CVE-2026-31668 linux linux kernel: Incomplete Cleanup

9.8 criticalEPSS 0.4%Fix available

Critical (9.8) in linux linux kernel. EPSS 0.4% estimated probability of exploitation activity in the next 30 days.

On this page
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.

Severity

CVSS 3.1

9.8 critical
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS
0.4% (unchanged from 0.4% a week ago; 0.4% 30 days ago) estimated probability of exploitation activity in the next 30 days; 39th percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: yes · Technical impact: total, assessed 2026-10-16. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-459 Incomplete Cleanup
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-31668 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-31668?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-31668?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-31668 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Linux4.10 and later

Fixed in

ProductRelease lineFixed in
Linux5.105.10.253
Linux5.155.15.203
Linux6.16.1.169
Linux6.66.6.135
Linux6.126.12.82
Linux6.186.18.23
Linux6.196.19.13
Linuxlater releases7.0

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12linux6.1.170-1DEBIAN-CVE-2026-31668
Debian13linux6.12.85-1DEBIAN-CVE-2026-31668
Debian14linux6.19.13-1DEBIAN-CVE-2026-31668
Ubuntu16.04:LTSlinux-hwe-edgeno fix listedUBUNTU-CVE-2026-31668
Ubuntu18.04:LTSlinux-gcp, linux-hwe, linux-oem and 12 moreno fix listedUBUNTU-CVE-2026-31668
Ubuntu20.04:LTSlinux-gke, linux-gkeop, linux-riscv and 26 moreno fix listedUBUNTU-CVE-2026-31668
Ubuntu22.04:LTSlinux5.15.0-185.195UBUNTU-CVE-2026-31668 USN-8493-1
Ubuntu22.04:LTSlinux-aws5.15.0-1111.118UBUNTU-CVE-2026-31668 USN-8493-1
Ubuntu22.04:LTSlinux-aws-6.86.8.0-1060.63~22.04.1UBUNTU-CVE-2026-31668 USN-8492-2
Ubuntu22.04:LTSlinux-azure, linux-azure-fde5.15.0-1116.125UBUNTU-CVE-2026-31668 USN-8493-1
Ubuntu22.04:LTSlinux-azure-6.86.8.0-1063.71~22.04.1UBUNTU-CVE-2026-31668 USN-8606-1
Ubuntu22.04:LTSlinux-azure-fde-6.86.8.0-1062.69~22.04.1UBUNTU-CVE-2026-31668 USN-8609-1
Ubuntu22.04:LTSlinux-gcp5.15.0-1111.121UBUNTU-CVE-2026-31668 USN-8493-1
Ubuntu22.04:LTSlinux-gcp-6.86.8.0-1063.69~22.04.1UBUNTU-CVE-2026-31668 USN-8492-2
Ubuntu22.04:LTSlinux-gke5.15.0-1107.113UBUNTU-CVE-2026-31668 USN-8493-1
117 more for Ubuntu in the JSON and on Ubuntu's page.
SUSELinux Enterprise High Availability Extension 15 SP7, Linux Enterprise Live Patching 15 SP7, Linux Enterprise Module for Legacy 15 SP7 and 1 morekernel-default6.4.0-150700.53.55.1SUSE-SU-2026:2238-1
SUSELinux Enterprise Live Patching 12 SP5kernel-default4.12.14-122.317.1SUSE-SU-2026:2450-1
SUSELinux Enterprise Live Patching 12 SP5kgraft-patch-SLE12-SP5_Update_841-8.7.1SUSE-SU-2026:2450-1
SUSELinux Enterprise Live Patching 15 SP7kernel-livepatch-SLE15-SP7_Update_151-150700.15.3.1SUSE-SU-2026:2238-1
SUSELinux Enterprise Module for Basesystem 15 SP7kernel-64kb, kernel-source, kernel-default and 1 more6.4.0-150700.53.55.1SUSE-SU-2026:2238-1
SUSELinux Enterprise Module for Basesystem 15 SP7kernel-default-base6.4.0-150700.53.55.1.150700.17.33.1SUSE-SU-2026:2238-1
SUSELinux Enterprise Module for Development Tools 15 SP7kernel-docs, kernel-syms, kernel-source and 1 more6.4.0-150700.53.55.1SUSE-SU-2026:2238-1
SUSELinux Enterprise Module for Public Cloud 15 SP7kernel-azure6.4.0-150700.53.55.1SUSE-SU-2026:2238-1
SUSELinux Enterprise Server 12 SP5-LTSS, Linux Enterprise Server LTSS Extended Security 12 SP5kernel-syms, kernel-source, kernel-default4.12.14-122.317.1SUSE-SU-2026:2450-1
SUSELinux Micro Extras 6.2kernel-syms, kernel-obs-build6.12.0-160000.33.1SUSE-SU-2026:21834-1
Azure Linux3kernel6.6.137.1-1AZL-83813
Alpaquita23linux-lts6.1.170-r0BELL-CVE-2026-31668
Alpaquita25linux-lts6.12.85-r0BELL-CVE-2026-31668
Alpaquitastreamlinux-lts6.18.35-r1BELL-CVE-2026-31668

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; SUSE security data, CC BY 4.0; Microsoft's Azure Linux vulnerability data, MIT; BellSoft's OSV database, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · SUSE · Alpaquita.

Red Hat

Red Hat rates this Low.

Red Hat's statement

The patch fixes a routing logic flaw in the SRv6 seg6 lwtunnel implementation. Previously, each encap route had a single dst_cache stored in struct seg6_lwt. That cache was shared by both seg6_input_core and seg6_output_core. These two code paths may perform the post encapsulation SID lookup under different routing contexts such as rules that match on the ingress interface or VRF based table selection. With one shared cache, whichever path executed first populated the cache. The other path then reused the cached dst blindly and could bypass its own lookup. This is best classified as a logic or policy enforcement issue rather than memory corruption.

Red Hat's mitigation

Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.

ProductPackageStateAdvisory
Red Hat Enterprise Linux 10kernelFix deferred
Red Hat Enterprise Linux 6kernelNot affected
Red Hat Enterprise Linux 7kernelNot affected
Red Hat Enterprise Linux 7kernel-rtNot affected
Red Hat Enterprise Linux 8kernelNot affected
Red Hat Enterprise Linux 8kernel-rtNot affected
Red Hat Enterprise Linux 9kernelFix deferred
Red Hat Enterprise Linux 9kernel-rtFix deferred

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-31668.

References

Check your stackJSON