Vulnerability · Published Sep 17, 2026 · Assigned by Linux

CVE-2026-90083net/sched: act_ife: Only operate on Ethernet frames

Unrated

In plain English

A 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 13% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.

Severity (CVSS )–Not rated
Exploit odds (30 days)0.2%top 87.3% 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/sched: act_ife: Only operate on Ethernet frames act_ife encapsulates/decapsulates the original Ethernet header and uses skb->dev->hard_header_len as the length of that header. That is only correct for Ethernet devices: on a device where hard_header_len does not match the L2 header that was actually pulled (PPP reports PPP_HDRLEN while nothing is stripped on ingress), the ingress skb_push()/skb_pull() use the wrong length and can hit skb_under_panic when headroom is tight. IFE is Ethernet-only by design - it builds an outer ethhdr, rewrites h_source/h_dest/h_proto, and calls eth_type_trans() on decode - so instead of trying to make the offsets work for arbitrary link types, simply drop packets that do not carry an Ethernet header. Checking skb->dev->type alone is not enough. We have to cater for a corner case where mirred can redirect an skb from a non-Ethernet device to an Ethernet one, and skb->dev then says nothing about the framing the skb actually has: an skb redirected from ppp0 reaches the target's ingress hook with mac_len 0 and no Ethernet header at all. So at ingress also require mac_len to be ETH_HLEN. On egress mac_len is not maintained, so the device type is all we have; a bogus redirect there yields a malformed frame rather than an out-of-bounds push, and it would be malformed with or without IFE. That corner case is not theoretical - redirecting from ppp0 into a veth that has an ife encode action on its ingress hook panics without this patch: skbuff: skb_under_panic: len:98 put:14 head:ffff88800e410000 data:ffff88800e40fff5 tail:0x57 end:0x640 dev:veth3 kernel BUG at net/core/skbuff.c:214! Call Trace: skb_push (net/core/skbuff.c:224 net/core/skbuff.c:2657) tcf_ife_act (net/sched/act_ife.c:829 net/sched/act_ife.c:874) tc_run (net/core/dev.c:4463) netif_receive_skb (net/core/dev.c:6463 net/core/dev.c:6522) tcf_mirred_to_dev (net/sched/act_mirred.c:248 net/sched/act_mirred.c:328) tcf_mirred_act (net/sched/act_mirred.c:489) tc_run (net/core/dev.c:4463) process_backlog (net/core/dev.c:6728) With Ethernet framing guaranteed, use ETH_HLEN instead of hard_header_len.

Affected packages & fixed versions

EcosystemPackageFixed inAdvisory
Debian:12linuxno fix listedDEBIAN-CVE-2026-90083
Debian:13linux6.12.115-2DEBIAN-CVE-2026-90083
Debian:14linux7.2.6-1DEBIAN-CVE-2026-90083
Ubuntu:22.04:LTSlinuxno fix listedUBUNTU-CVE-2026-90083
Ubuntu:24.04:LTSlinuxno fix listedUBUNTU-CVE-2026-90083
Ubuntu:26.04:LTSlinux7.0.0-42.42UBUNTU-CVE-2026-90083
Ubuntu:22.04:LTSlinux-allwinner-5.19no fix listedUBUNTU-CVE-2026-90083
Ubuntu:22.04:LTSlinux-awsno fix listedUBUNTU-CVE-2026-90083
Ubuntu:24.04:LTSlinux-awsno fix listedUBUNTU-CVE-2026-90083
Ubuntu:26.04:LTSlinux-aws7.0.0-1016.17UBUNTU-CVE-2026-90083
Ubuntu:22.04:LTSlinux-aws-5.19no fix listedUBUNTU-CVE-2026-90083
Ubuntu:24.04:LTSlinux-aws-6.14no fix listedUBUNTU-CVE-2026-90083
Ubuntu:24.04:LTSlinux-aws-6.17no fix listedUBUNTU-CVE-2026-90083
Ubuntu:22.04:LTSlinux-aws-6.2no fix listedUBUNTU-CVE-2026-90083
Ubuntu:22.04:LTSlinux-aws-6.5no fix listedUBUNTU-CVE-2026-90083
Ubuntu:22.04:LTSlinux-aws-6.8no fix listedUBUNTU-CVE-2026-90083
Ubuntu:24.04:LTSlinux-aws-7.0no fix listedUBUNTU-CVE-2026-90083
Ubuntu:22.04:LTSlinux-azureno fix listedUBUNTU-CVE-2026-90083
Ubuntu:24.04:LTSlinux-azureno fix listedUBUNTU-CVE-2026-90083
Ubuntu:26.04:LTSlinux-azureno fix listedUBUNTU-CVE-2026-90083
Ubuntu:22.04:LTSlinux-azure-5.19no fix listedUBUNTU-CVE-2026-90083
Ubuntu:24.04:LTSlinux-azure-6.11no fix listedUBUNTU-CVE-2026-90083
Ubuntu:24.04:LTSlinux-azure-6.14no fix listedUBUNTU-CVE-2026-90083
Ubuntu:24.04:LTSlinux-azure-6.17no fix listedUBUNTU-CVE-2026-90083
Ubuntu:22.04:LTSlinux-azure-6.2no fix listedUBUNTU-CVE-2026-90083
Ubuntu:22.04:LTSlinux-azure-6.5no fix listedUBUNTU-CVE-2026-90083
Ubuntu:22.04:LTSlinux-azure-6.8no fix listedUBUNTU-CVE-2026-90083
Ubuntu:24.04:LTSlinux-azure-7.0no fix listedUBUNTU-CVE-2026-90083
Ubuntu:22.04:LTSlinux-azure-fdeno fix listedUBUNTU-CVE-2026-90083
Ubuntu:24.04:LTSlinux-azure-fdeno fix listedUBUNTU-CVE-2026-90083
Ubuntu:26.04:LTSlinux-azure-fdeno fix listedUBUNTU-CVE-2026-90083
Ubuntu:22.04:LTSlinux-azure-fde-5.19no fix listedUBUNTU-CVE-2026-90083
Ubuntu:24.04:LTSlinux-azure-fde-6.14no fix listedUBUNTU-CVE-2026-90083
Ubuntu:24.04:LTSlinux-azure-fde-6.17no fix listedUBUNTU-CVE-2026-90083
Ubuntu:22.04:LTSlinux-azure-fde-6.2no fix listedUBUNTU-CVE-2026-90083
Ubuntu:22.04:LTSlinux-azure-fde-6.8no fix listedUBUNTU-CVE-2026-90083
Ubuntu:24.04:LTSlinux-azure-fde-7.0no fix listedUBUNTU-CVE-2026-90083
Ubuntu:24.04:LTSlinux-azure-nvidiano fix listedUBUNTU-CVE-2026-90083
Ubuntu:24.04:LTSlinux-azure-nvidia-6.14no fix listedUBUNTU-CVE-2026-90083
Ubuntu:22.04:LTSlinux-gcpno fix listedUBUNTU-CVE-2026-90083
Ubuntu:24.04:LTSlinux-gcpno fix listedUBUNTU-CVE-2026-90083
Ubuntu:26.04:LTSlinux-gcp7.0.0-1016.18UBUNTU-CVE-2026-90083
Ubuntu:22.04:LTSlinux-gcp-5.19no fix listedUBUNTU-CVE-2026-90083
Ubuntu:24.04:LTSlinux-gcp-6.11no fix listedUBUNTU-CVE-2026-90083
Ubuntu:24.04:LTSlinux-gcp-6.14no fix listedUBUNTU-CVE-2026-90083
Ubuntu:24.04:LTSlinux-gcp-6.17no fix listedUBUNTU-CVE-2026-90083
Ubuntu:22.04:LTSlinux-gcp-6.2no fix listedUBUNTU-CVE-2026-90083
Ubuntu:22.04:LTSlinux-gcp-6.5no fix listedUBUNTU-CVE-2026-90083
Ubuntu:22.04:LTSlinux-gcp-6.8no fix listedUBUNTU-CVE-2026-90083
Ubuntu:24.04:LTSlinux-gcp-7.0no fix listedUBUNTU-CVE-2026-90083
Ubuntu:22.04:LTSlinux-gkeno fix listedUBUNTU-CVE-2026-90083
Ubuntu:24.04:LTSlinux-gkeno fix listedUBUNTU-CVE-2026-90083
Ubuntu:26.04:LTSlinux-gkeno fix listedUBUNTU-CVE-2026-90083
Ubuntu:22.04:LTSlinux-gkeopno fix listedUBUNTU-CVE-2026-90083
Ubuntu:24.04:LTSlinux-gkeopno fix listedUBUNTU-CVE-2026-90083
Ubuntu:22.04:LTSlinux-hwe-5.19no fix listedUBUNTU-CVE-2026-90083
Ubuntu:24.04:LTSlinux-hwe-6.11no fix listedUBUNTU-CVE-2026-90083
Ubuntu:24.04:LTSlinux-hwe-6.14no fix listedUBUNTU-CVE-2026-90083
Ubuntu:24.04:LTSlinux-hwe-6.17no fix listedUBUNTU-CVE-2026-90083
Ubuntu:22.04:LTSlinux-hwe-6.2no fix listedUBUNTU-CVE-2026-90083
Ubuntu:22.04:LTSlinux-hwe-6.5no fix listedUBUNTU-CVE-2026-90083
Ubuntu:22.04:LTSlinux-hwe-6.8no fix listedUBUNTU-CVE-2026-90083
Ubuntu:24.04:LTSlinux-hwe-7.07.0.0-42.42~24.04.1UBUNTU-CVE-2026-90083
Ubuntu:22.04:LTSlinux-ibmno fix listedUBUNTU-CVE-2026-90083
Ubuntu:24.04:LTSlinux-ibmno fix listedUBUNTU-CVE-2026-90083
Ubuntu:26.04:LTSlinux-ibm7.0.0-1017.17UBUNTU-CVE-2026-90083
Ubuntu:22.04:LTSlinux-ibm-6.8no fix listedUBUNTU-CVE-2026-90083
Ubuntu:22.04:LTSlinux-intel-iot-realtimeno fix listedUBUNTU-CVE-2026-90083
Ubuntu:22.04:LTSlinux-intel-iotgno fix listedUBUNTU-CVE-2026-90083
Ubuntu:22.04:LTSlinux-kvmno fix listedUBUNTU-CVE-2026-90083
Ubuntu:22.04:LTSlinux-lowlatencyno fix listedUBUNTU-CVE-2026-90083
Ubuntu:24.04:LTSlinux-lowlatencyno fix listedUBUNTU-CVE-2026-90083
Ubuntu:22.04:LTSlinux-lowlatency-hwe-5.19no fix listedUBUNTU-CVE-2026-90083
Ubuntu:24.04:LTSlinux-lowlatency-hwe-6.11no fix listedUBUNTU-CVE-2026-90083
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.2no fix listedUBUNTU-CVE-2026-90083
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.5no fix listedUBUNTU-CVE-2026-90083
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.8no fix listedUBUNTU-CVE-2026-90083
Ubuntu:22.04:LTSlinux-nvidiano fix listedUBUNTU-CVE-2026-90083
Ubuntu:24.04:LTSlinux-nvidiano fix listedUBUNTU-CVE-2026-90083
Ubuntu:26.04:LTSlinux-nvidiano fix listedUBUNTU-CVE-2026-90083
Ubuntu:24.04:LTSlinux-nvidia-6.11no fix listedUBUNTU-CVE-2026-90083
Ubuntu:24.04:LTSlinux-nvidia-6.17no fix listedUBUNTU-CVE-2026-90083
Ubuntu:22.04:LTSlinux-nvidia-6.2no fix listedUBUNTU-CVE-2026-90083
Ubuntu:22.04:LTSlinux-nvidia-6.5no fix listedUBUNTU-CVE-2026-90083
Ubuntu:22.04:LTSlinux-nvidia-6.8no fix listedUBUNTU-CVE-2026-90083
Ubuntu:24.04:LTSlinux-nvidia-7.0no fix listedUBUNTU-CVE-2026-90083
Ubuntu:26.04:LTSlinux-nvidia-bosno fix listedUBUNTU-CVE-2026-90083
Ubuntu:24.04:LTSlinux-nvidia-lowlatencyno fix listedUBUNTU-CVE-2026-90083
Ubuntu:22.04:LTSlinux-nvidia-tegrano fix listedUBUNTU-CVE-2026-90083
Ubuntu:24.04:LTSlinux-nvidia-tegrano fix listedUBUNTU-CVE-2026-90083
Ubuntu:22.04:LTSlinux-nvidia-tegra-igxno fix listedUBUNTU-CVE-2026-90083
Ubuntu:22.04:LTSlinux-oem-5.17no fix listedUBUNTU-CVE-2026-90083
Ubuntu:22.04:LTSlinux-oem-6.0no fix listedUBUNTU-CVE-2026-90083
Ubuntu:22.04:LTSlinux-oem-6.1no fix listedUBUNTU-CVE-2026-90083
Ubuntu:24.04:LTSlinux-oem-6.11no fix listedUBUNTU-CVE-2026-90083
Ubuntu:24.04:LTSlinux-oem-6.14no fix listedUBUNTU-CVE-2026-90083
Ubuntu:24.04:LTSlinux-oem-6.17no fix listedUBUNTU-CVE-2026-90083
Ubuntu:22.04:LTSlinux-oem-6.5no fix listedUBUNTU-CVE-2026-90083
Ubuntu:24.04:LTSlinux-oem-6.8no fix listedUBUNTU-CVE-2026-90083
Ubuntu:26.04:LTSlinux-oem-7.07.0.0-1017.17UBUNTU-CVE-2026-90083
Ubuntu:22.04:LTSlinux-oracleno fix listedUBUNTU-CVE-2026-90083
Ubuntu:24.04:LTSlinux-oracleno fix listedUBUNTU-CVE-2026-90083
Ubuntu:26.04:LTSlinux-oracle7.0.0-1015.16UBUNTU-CVE-2026-90083
Ubuntu:24.04:LTSlinux-oracle-6.14no fix listedUBUNTU-CVE-2026-90083
Ubuntu:24.04:LTSlinux-oracle-6.17no fix listedUBUNTU-CVE-2026-90083
Ubuntu:22.04:LTSlinux-oracle-6.5no fix listedUBUNTU-CVE-2026-90083
Ubuntu:22.04:LTSlinux-oracle-6.8no fix listedUBUNTU-CVE-2026-90083
Ubuntu:24.04:LTSlinux-oracle-7.0no fix listedUBUNTU-CVE-2026-90083
Ubuntu:22.04:LTSlinux-raspino fix listedUBUNTU-CVE-2026-90083
Ubuntu:24.04:LTSlinux-raspino fix listedUBUNTU-CVE-2026-90083
Ubuntu:26.04:LTSlinux-raspino fix listedUBUNTU-CVE-2026-90083
Ubuntu:24.04:LTSlinux-raspi-realtimeno fix listedUBUNTU-CVE-2026-90083
Ubuntu:22.04:LTSlinux-realtimeno fix listedUBUNTU-CVE-2026-90083
Ubuntu:24.04:LTSlinux-realtimeno fix listedUBUNTU-CVE-2026-90083
Ubuntu:26.04:LTSlinux-realtimeno fix listedUBUNTU-CVE-2026-90083
Ubuntu:22.04:LTSlinux-riscvno fix listedUBUNTU-CVE-2026-90083
Ubuntu:24.04:LTSlinux-riscvno fix listedUBUNTU-CVE-2026-90083
Ubuntu:26.04:LTSlinux-riscv7.0.0-42.42.1UBUNTU-CVE-2026-90083
Ubuntu:22.04:LTSlinux-riscv-5.19no fix listedUBUNTU-CVE-2026-90083
Ubuntu:24.04:LTSlinux-riscv-6.14no fix listedUBUNTU-CVE-2026-90083
Ubuntu:24.04:LTSlinux-riscv-6.17no fix listedUBUNTU-CVE-2026-90083
Ubuntu:22.04:LTSlinux-riscv-6.5no fix listedUBUNTU-CVE-2026-90083
Ubuntu:22.04:LTSlinux-riscv-6.8no fix listedUBUNTU-CVE-2026-90083
Ubuntu:24.04:LTSlinux-riscv-7.07.0.0-42.42.1~24.04.1UBUNTU-CVE-2026-90083
Ubuntu:22.04:LTSlinux-starfive-5.19no fix listedUBUNTU-CVE-2026-90083
Ubuntu:22.04:LTSlinux-starfive-6.2no fix listedUBUNTU-CVE-2026-90083
Ubuntu:22.04:LTSlinux-starfive-6.5no fix listedUBUNTU-CVE-2026-90083
Ubuntu:24.04:LTSlinux-vmwareno fix listedUBUNTU-CVE-2026-90083
Ubuntu:24.04:LTSlinux-xilinxno fix listedUBUNTU-CVE-2026-90083
Ubuntu:22.04:LTSlinux-xilinx-zynqmpno fix listedUBUNTU-CVE-2026-90083

Affected products (as reported)

VendorProductVersions
Linux Linux 295a6e06d21e1f469c9f38b00125a13b60ad4e7c – before 3c07621770b04f19b67e3af4a24b4d447826fbdd295a6e06d21e1f469c9f38b00125a13b60ad4e7c – before b951dd2fd5ede007474fc134ecb5639e1f86f5de295a6e06d21e1f469c9f38b00125a13b60ad4e7c – before 13dddf87a1f89557920f9b437a21ea0b7225f828295a6e06d21e1f469c9f38b00125a13b60ad4e7c – before d218ea7df6eba076171f2d4897a429a31f2139f0295a6e06d21e1f469c9f38b00125a13b60ad4e7c – before 138b0054021fd7d57bc3eb68b3f4e2bcec037849295a6e06d21e1f469c9f38b00125a13b60ad4e7c – before 5b483f7791b079bb97d411f1066652ff659207ff
Linux Linux 4.11

References