Vulnerability · Published Sep 25, 2026 · Assigned by Linux

CVE-2026-97612net: mpls: clear inner_protocol when the last label is popped

High 7.8

In plain English

A high-severity security flaw in Linux from Linux. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 0.2% (higher than 6% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.

Severity (CVSS 3.1)7.8High
Exploit odds (30 days)0.2%top 93.7% of all CVEs
Exploited in the wildNo reportsnot in CISA KEV
Attack toolingNoneno public tooling known

Official description

In the Linux kernel, the following vulnerability has been resolved: net: mpls: clear inner_protocol when the last label is popped skb_mpls_push() records the pre-encapsulation network header once, gated on !skb->inner_protocol. skb_mpls_pop() never clears that record, so it outlives the encapsulation it describes. Open vSwitch can then re-push MPLS onto a packet whose inner_network_header still points at the older, deeper offset: push a label, pop every label, recirculate (ovs_flow_key_update() re-derives key->eth.type and resets network_header, but leaves inner_*), then push again. ovs_fragment() trusts the record: skb->network_header = skb->inner_network_header; so skb_network_offset() goes negative. The bound check is signed: if (skb_network_offset(skb) > MAX_L2_LEN) a negative offset passes it, and prepare_frag() widens the value: unsigned int hlen = skb_network_offset(skb); memcpy(&data->l2_data, skb->data, hlen); which is a ~4GiB memcpy out of a 30-byte per-CPU buffer. Reproduced on v7.3-rc1. RDX is the truncated length, (unsigned int)(-8): BUG: unable to handle page fault for address: ffffe8ffffc16000 #PF: supervisor write access in kernel mode Oops: 0002 [#1] SMP KASAN NOPTI RIP: 0010:memcpy+0x8/0x20 RDX: 00000000fffffff8 RSI: ffff888105d732db RDI: ffffe8ffffc16000 prepare_frag+0x3df/0x4e0 ovs_fragment+0x589/0x7e0 do_output+0x4ce/0x5e0 do_execute_actions+0x55d2/0x7b30 ovs_execute_actions+0xea/0x450 Same root-cause shape as commit 975b5b067f52 ("ipv6: sr: restore network header before routing and forwarding"): a stale network header offset reaching a consumer that widens it. Here it originates in the MPLS push/pop path. Clear inner_protocol once the packet is no longer MPLS, so a later push re-records the current header. net/sched/act_mpls.c is the only other skb_mpls_pop() caller and gets the same fix; sch_frag.c saves and restores inner_protocol around fragmentation in the same way OVS does.

Affected packages & fixed versions

EcosystemPackageFixed inAdvisory
Debian:12linux6.1.190-1DEBIAN-CVE-2026-97612
Debian:13linux6.12.111-1DEBIAN-CVE-2026-97612
Debian:14linux7.2.7-1DEBIAN-CVE-2026-97612
Debian:12linux-6.126.12.111-1~deb12u1DEBIAN-CVE-2026-97612
Ubuntu:22.04:LTSlinux5.15.0-202.212UBUNTU-CVE-2026-97612
Ubuntu:24.04:LTSlinuxno fix listedUBUNTU-CVE-2026-97612
Ubuntu:26.04:LTSlinux7.0.0-42.42UBUNTU-CVE-2026-97612
Ubuntu:22.04:LTSlinux-allwinner-5.19no fix listedUBUNTU-CVE-2026-97612
Ubuntu:22.04:LTSlinux-aws5.15.0-1119.126UBUNTU-CVE-2026-97612
Ubuntu:24.04:LTSlinux-awsno fix listedUBUNTU-CVE-2026-97612
Ubuntu:26.04:LTSlinux-aws7.0.0-1016.17UBUNTU-CVE-2026-97612
Ubuntu:22.04:LTSlinux-aws-5.19no fix listedUBUNTU-CVE-2026-97612
Ubuntu:24.04:LTSlinux-aws-6.14no fix listedUBUNTU-CVE-2026-97612
Ubuntu:24.04:LTSlinux-aws-6.17no fix listedUBUNTU-CVE-2026-97612
Ubuntu:22.04:LTSlinux-aws-6.2no fix listedUBUNTU-CVE-2026-97612
Ubuntu:22.04:LTSlinux-aws-6.5no fix listedUBUNTU-CVE-2026-97612
Ubuntu:22.04:LTSlinux-aws-6.8no fix listedUBUNTU-CVE-2026-97612
Ubuntu:24.04:LTSlinux-aws-7.0no fix listedUBUNTU-CVE-2026-97612
Ubuntu:22.04:LTSlinux-azure5.15.0-1125.134UBUNTU-CVE-2026-97612
Ubuntu:24.04:LTSlinux-azureno fix listedUBUNTU-CVE-2026-97612
Ubuntu:26.04:LTSlinux-azureno fix listedUBUNTU-CVE-2026-97612
Ubuntu:22.04:LTSlinux-azure-5.19no fix listedUBUNTU-CVE-2026-97612
Ubuntu:24.04:LTSlinux-azure-6.11no fix listedUBUNTU-CVE-2026-97612
Ubuntu:24.04:LTSlinux-azure-6.14no fix listedUBUNTU-CVE-2026-97612
Ubuntu:24.04:LTSlinux-azure-6.17no fix listedUBUNTU-CVE-2026-97612
Ubuntu:22.04:LTSlinux-azure-6.2no fix listedUBUNTU-CVE-2026-97612
Ubuntu:22.04:LTSlinux-azure-6.5no fix listedUBUNTU-CVE-2026-97612
Ubuntu:22.04:LTSlinux-azure-6.8no fix listedUBUNTU-CVE-2026-97612
Ubuntu:24.04:LTSlinux-azure-7.0no fix listedUBUNTU-CVE-2026-97612
Ubuntu:22.04:LTSlinux-azure-fde5.15.0-1124.133UBUNTU-CVE-2026-97612
Ubuntu:24.04:LTSlinux-azure-fdeno fix listedUBUNTU-CVE-2026-97612
Ubuntu:26.04:LTSlinux-azure-fdeno fix listedUBUNTU-CVE-2026-97612
Ubuntu:22.04:LTSlinux-azure-fde-5.19no fix listedUBUNTU-CVE-2026-97612
Ubuntu:24.04:LTSlinux-azure-fde-6.14no fix listedUBUNTU-CVE-2026-97612
Ubuntu:24.04:LTSlinux-azure-fde-6.17no fix listedUBUNTU-CVE-2026-97612
Ubuntu:22.04:LTSlinux-azure-fde-6.2no fix listedUBUNTU-CVE-2026-97612
Ubuntu:22.04:LTSlinux-azure-fde-6.8no fix listedUBUNTU-CVE-2026-97612
Ubuntu:24.04:LTSlinux-azure-fde-7.0no fix listedUBUNTU-CVE-2026-97612
Ubuntu:24.04:LTSlinux-azure-nvidiano fix listedUBUNTU-CVE-2026-97612
Ubuntu:24.04:LTSlinux-azure-nvidia-6.14no fix listedUBUNTU-CVE-2026-97612
Ubuntu:22.04:LTSlinux-gcp5.15.0-1120.130UBUNTU-CVE-2026-97612
Ubuntu:24.04:LTSlinux-gcpno fix listedUBUNTU-CVE-2026-97612
Ubuntu:26.04:LTSlinux-gcp7.0.0-1016.18UBUNTU-CVE-2026-97612
Ubuntu:22.04:LTSlinux-gcp-5.19no fix listedUBUNTU-CVE-2026-97612
Ubuntu:24.04:LTSlinux-gcp-6.11no fix listedUBUNTU-CVE-2026-97612
Ubuntu:24.04:LTSlinux-gcp-6.14no fix listedUBUNTU-CVE-2026-97612
Ubuntu:24.04:LTSlinux-gcp-6.17no fix listedUBUNTU-CVE-2026-97612
Ubuntu:22.04:LTSlinux-gcp-6.2no fix listedUBUNTU-CVE-2026-97612
Ubuntu:22.04:LTSlinux-gcp-6.5no fix listedUBUNTU-CVE-2026-97612
Ubuntu:22.04:LTSlinux-gcp-6.8no fix listedUBUNTU-CVE-2026-97612
Ubuntu:24.04:LTSlinux-gcp-7.0no fix listedUBUNTU-CVE-2026-97612
Ubuntu:22.04:LTSlinux-gke5.15.0-1115.121UBUNTU-CVE-2026-97612
Ubuntu:24.04:LTSlinux-gkeno fix listedUBUNTU-CVE-2026-97612
Ubuntu:26.04:LTSlinux-gkeno fix listedUBUNTU-CVE-2026-97612
Ubuntu:22.04:LTSlinux-gkeop5.15.0-1102.110UBUNTU-CVE-2026-97612
Ubuntu:24.04:LTSlinux-gkeopno fix listedUBUNTU-CVE-2026-97612
Ubuntu:22.04:LTSlinux-hwe-5.19no fix listedUBUNTU-CVE-2026-97612
Ubuntu:24.04:LTSlinux-hwe-6.11no fix listedUBUNTU-CVE-2026-97612
Ubuntu:24.04:LTSlinux-hwe-6.14no fix listedUBUNTU-CVE-2026-97612
Ubuntu:24.04:LTSlinux-hwe-6.17no fix listedUBUNTU-CVE-2026-97612
Ubuntu:22.04:LTSlinux-hwe-6.2no fix listedUBUNTU-CVE-2026-97612
Ubuntu:22.04:LTSlinux-hwe-6.5no fix listedUBUNTU-CVE-2026-97612
Ubuntu:22.04:LTSlinux-hwe-6.8no fix listedUBUNTU-CVE-2026-97612
Ubuntu:24.04:LTSlinux-hwe-7.07.0.0-42.42~24.04.1UBUNTU-CVE-2026-97612
Ubuntu:22.04:LTSlinux-ibm5.15.0-1113.117UBUNTU-CVE-2026-97612
Ubuntu:24.04:LTSlinux-ibmno fix listedUBUNTU-CVE-2026-97612
Ubuntu:26.04:LTSlinux-ibm7.0.0-1017.17UBUNTU-CVE-2026-97612
Ubuntu:22.04:LTSlinux-ibm-6.8no fix listedUBUNTU-CVE-2026-97612
Ubuntu:22.04:LTSlinux-intel-iot-realtimeno fix listedUBUNTU-CVE-2026-97612
Ubuntu:22.04:LTSlinux-intel-iotg5.15.0-1114.120UBUNTU-CVE-2026-97612
Ubuntu:22.04:LTSlinux-kvm5.15.0-1111.116UBUNTU-CVE-2026-97612
Ubuntu:22.04:LTSlinux-lowlatency5.15.0-197.207UBUNTU-CVE-2026-97612
Ubuntu:24.04:LTSlinux-lowlatencyno fix listedUBUNTU-CVE-2026-97612
Ubuntu:22.04:LTSlinux-lowlatency-hwe-5.19no fix listedUBUNTU-CVE-2026-97612
Ubuntu:24.04:LTSlinux-lowlatency-hwe-6.11no fix listedUBUNTU-CVE-2026-97612
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.2no fix listedUBUNTU-CVE-2026-97612
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.5no fix listedUBUNTU-CVE-2026-97612
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.8no fix listedUBUNTU-CVE-2026-97612
Ubuntu:22.04:LTSlinux-nvidia5.15.0-1114.115UBUNTU-CVE-2026-97612
Ubuntu:24.04:LTSlinux-nvidiano fix listedUBUNTU-CVE-2026-97612
Ubuntu:26.04:LTSlinux-nvidiano fix listedUBUNTU-CVE-2026-97612
Ubuntu:24.04:LTSlinux-nvidia-6.11no fix listedUBUNTU-CVE-2026-97612
Ubuntu:24.04:LTSlinux-nvidia-6.17no fix listedUBUNTU-CVE-2026-97612
Ubuntu:22.04:LTSlinux-nvidia-6.2no fix listedUBUNTU-CVE-2026-97612
Ubuntu:22.04:LTSlinux-nvidia-6.5no fix listedUBUNTU-CVE-2026-97612
Ubuntu:22.04:LTSlinux-nvidia-6.8no fix listedUBUNTU-CVE-2026-97612
Ubuntu:24.04:LTSlinux-nvidia-7.0no fix listedUBUNTU-CVE-2026-97612
Ubuntu:26.04:LTSlinux-nvidia-bosno fix listedUBUNTU-CVE-2026-97612
Ubuntu:24.04:LTSlinux-nvidia-lowlatencyno fix listedUBUNTU-CVE-2026-97612
Ubuntu:22.04:LTSlinux-nvidia-tegra5.15.0-1070.72UBUNTU-CVE-2026-97612
Ubuntu:24.04:LTSlinux-nvidia-tegrano fix listedUBUNTU-CVE-2026-97612
Ubuntu:22.04:LTSlinux-nvidia-tegra-igx5.15.0-1059.59UBUNTU-CVE-2026-97612
Ubuntu:22.04:LTSlinux-oem-5.17no fix listedUBUNTU-CVE-2026-97612
Ubuntu:22.04:LTSlinux-oem-6.0no fix listedUBUNTU-CVE-2026-97612
Ubuntu:22.04:LTSlinux-oem-6.1no fix listedUBUNTU-CVE-2026-97612
Ubuntu:24.04:LTSlinux-oem-6.11no fix listedUBUNTU-CVE-2026-97612
Ubuntu:24.04:LTSlinux-oem-6.14no fix listedUBUNTU-CVE-2026-97612
Ubuntu:24.04:LTSlinux-oem-6.17no fix listedUBUNTU-CVE-2026-97612
Ubuntu:22.04:LTSlinux-oem-6.5no fix listedUBUNTU-CVE-2026-97612
Ubuntu:24.04:LTSlinux-oem-6.8no fix listedUBUNTU-CVE-2026-97612
Ubuntu:26.04:LTSlinux-oem-7.07.0.0-1017.17UBUNTU-CVE-2026-97612
Ubuntu:22.04:LTSlinux-oracle5.15.0-1116.122UBUNTU-CVE-2026-97612
Ubuntu:24.04:LTSlinux-oracleno fix listedUBUNTU-CVE-2026-97612
Ubuntu:26.04:LTSlinux-oracle7.0.0-1015.16UBUNTU-CVE-2026-97612
Ubuntu:24.04:LTSlinux-oracle-6.14no fix listedUBUNTU-CVE-2026-97612
Ubuntu:24.04:LTSlinux-oracle-6.17no fix listedUBUNTU-CVE-2026-97612
Ubuntu:22.04:LTSlinux-oracle-6.5no fix listedUBUNTU-CVE-2026-97612
Ubuntu:22.04:LTSlinux-oracle-6.8no fix listedUBUNTU-CVE-2026-97612
Ubuntu:24.04:LTSlinux-oracle-7.0no fix listedUBUNTU-CVE-2026-97612
Ubuntu:22.04:LTSlinux-raspino fix listedUBUNTU-CVE-2026-97612
Ubuntu:24.04:LTSlinux-raspino fix listedUBUNTU-CVE-2026-97612
Ubuntu:26.04:LTSlinux-raspino fix listedUBUNTU-CVE-2026-97612
Ubuntu:24.04:LTSlinux-raspi-realtimeno fix listedUBUNTU-CVE-2026-97612
Ubuntu:22.04:LTSlinux-realtimeno fix listedUBUNTU-CVE-2026-97612
Ubuntu:24.04:LTSlinux-realtimeno fix listedUBUNTU-CVE-2026-97612
Ubuntu:26.04:LTSlinux-realtimeno fix listedUBUNTU-CVE-2026-97612
Ubuntu:22.04:LTSlinux-riscvno fix listedUBUNTU-CVE-2026-97612
Ubuntu:24.04:LTSlinux-riscvno fix listedUBUNTU-CVE-2026-97612
Ubuntu:26.04:LTSlinux-riscv7.0.0-42.42.1UBUNTU-CVE-2026-97612
Ubuntu:22.04:LTSlinux-riscv-5.19no fix listedUBUNTU-CVE-2026-97612
Ubuntu:24.04:LTSlinux-riscv-6.14no fix listedUBUNTU-CVE-2026-97612
Ubuntu:24.04:LTSlinux-riscv-6.17no fix listedUBUNTU-CVE-2026-97612
Ubuntu:22.04:LTSlinux-riscv-6.5no fix listedUBUNTU-CVE-2026-97612
Ubuntu:22.04:LTSlinux-riscv-6.8no fix listedUBUNTU-CVE-2026-97612
Ubuntu:24.04:LTSlinux-riscv-7.07.0.0-42.42.1~24.04.1UBUNTU-CVE-2026-97612
Ubuntu:22.04:LTSlinux-starfive-5.19no fix listedUBUNTU-CVE-2026-97612
Ubuntu:22.04:LTSlinux-starfive-6.2no fix listedUBUNTU-CVE-2026-97612
Ubuntu:22.04:LTSlinux-starfive-6.5no fix listedUBUNTU-CVE-2026-97612
Ubuntu:24.04:LTSlinux-vmwareno fix listedUBUNTU-CVE-2026-97612
Ubuntu:24.04:LTSlinux-xilinxno fix listedUBUNTU-CVE-2026-97612
Ubuntu:22.04:LTSlinux-xilinx-zynqmpno fix listedUBUNTU-CVE-2026-97612

Affected products (as reported)

VendorProductVersions
Linux Linux 48d2ab609b6bbecb7698487c8579bc40de9d6dfa – before 55ed97db27bffe29c21fdefd5d25601322c36ff848d2ab609b6bbecb7698487c8579bc40de9d6dfa – before 833ec2788322306407503b4cfc7745cd1f9d785f48d2ab609b6bbecb7698487c8579bc40de9d6dfa – before 38db09804b2616aa1e2fcdf97f0c3ae8b9dbdd3448d2ab609b6bbecb7698487c8579bc40de9d6dfa – before 0b3425fd0ecd515997956f7bb8a8a576b444ed6448d2ab609b6bbecb7698487c8579bc40de9d6dfa – before 011e17b5cae19b9f6a150923275e41c278de64f048d2ab609b6bbecb7698487c8579bc40de9d6dfa – before da8c3a7f5d3137fec4ff60a6248f5f6d66b6a63e48d2ab609b6bbecb7698487c8579bc40de9d6dfa – before b39120523475d6b436be7f6cb27d48064148a32748d2ab609b6bbecb7698487c8579bc40de9d6dfa – before 78a86d75a70e1e227711c72865c59b1422d0a5ae
Linux Linux 4.9

References