Vulnerability · Published Oct 18, 2026 · Assigned by Linux

CVE-2026-98796net: ethernet: mtk_eth_soc: allocate dummy netdev sooner

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

Severity (CVSS )–Not rated
Exploit odds (30 days)0.2%top 93.9% 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: ethernet: mtk_eth_soc: allocate dummy netdev sooner The RX rings and the shared NAPI are carried by an internal "dummy" netdev (eth->dummy_dev). mtk_probe() creates that dummy device, and adds the shared tx/rx NAPI to it, only after the MAC netdevs have been registered. That order has been there since the MT7623 support was added and leaves a window in which the netdevs are visible to the network core before the shared NAPI and the dummy device exist. If anything brings the first netdev up during that window (e.g. netifd opening the WAN link the instant the interface is registered), the first-open path runs without them. On NETSYS v2 and later SoCs mtk_rx_alloc() -> __xdp_rxq_info_reg() then dereferences eth->dummy_dev == NULL: WARNING: CPU: ... Missing net_device from driver in net/core/xdp.c and mtk_open() fails with -ENODEV. On NETSYS v1 SoCs (MT7621/MT7622/MT7623/MT7629) there is no page pool, so the same open instead calls napi_enable() on a napi_struct that netif_napi_add() has not initialised yet and dereferences a NULL napi->dev. Allocate the dummy netdev and add the shared tx/rx NAPI to it before the register_netdev() loop. Both the dummy-allocation failure and a register_netdev() failure now unwind through mtk_unreg_dev(), which unregisters the net_device notifiers and the netdevs registered so far, stopping a concurrently-opened netdev (ndo_stop) and its NAPI before the dummy carrier is freed. A netdev that opened during the window can also have queued the frame-engine reset worker (via the tx watchdog or phylink), so the probe error path now cancels eth->pending_work before freeing the shared state, as mtk_cleanup() already does on remove.

Affected packages & fixed versions

EcosystemPackageFixed inAdvisory
Debian:12linuxno fix listedDEBIAN-CVE-2026-98796
Debian:13linux6.12.113-1DEBIAN-CVE-2026-98796
Debian:14linux7.2.10-1DEBIAN-CVE-2026-98796
Debian:12linux-6.126.12.113-1~deb12u1DEBIAN-CVE-2026-98796
Ubuntu:22.04:LTSlinuxno fix listedUBUNTU-CVE-2026-98796
Ubuntu:24.04:LTSlinuxno fix listedUBUNTU-CVE-2026-98796
Ubuntu:26.04:LTSlinuxno fix listedUBUNTU-CVE-2026-98796
Ubuntu:22.04:LTSlinux-allwinner-5.19no fix listedUBUNTU-CVE-2026-98796
Ubuntu:22.04:LTSlinux-awsno fix listedUBUNTU-CVE-2026-98796
Ubuntu:24.04:LTSlinux-awsno fix listedUBUNTU-CVE-2026-98796
Ubuntu:26.04:LTSlinux-awsno fix listedUBUNTU-CVE-2026-98796
Ubuntu:22.04:LTSlinux-aws-5.19no fix listedUBUNTU-CVE-2026-98796
Ubuntu:24.04:LTSlinux-aws-6.14no fix listedUBUNTU-CVE-2026-98796
Ubuntu:24.04:LTSlinux-aws-6.17no fix listedUBUNTU-CVE-2026-98796
Ubuntu:22.04:LTSlinux-aws-6.2no fix listedUBUNTU-CVE-2026-98796
Ubuntu:22.04:LTSlinux-aws-6.5no fix listedUBUNTU-CVE-2026-98796
Ubuntu:22.04:LTSlinux-aws-6.8no fix listedUBUNTU-CVE-2026-98796
Ubuntu:24.04:LTSlinux-aws-7.0no fix listedUBUNTU-CVE-2026-98796
Ubuntu:22.04:LTSlinux-azureno fix listedUBUNTU-CVE-2026-98796
Ubuntu:24.04:LTSlinux-azureno fix listedUBUNTU-CVE-2026-98796
Ubuntu:26.04:LTSlinux-azureno fix listedUBUNTU-CVE-2026-98796
Ubuntu:22.04:LTSlinux-azure-5.19no fix listedUBUNTU-CVE-2026-98796
Ubuntu:24.04:LTSlinux-azure-6.11no fix listedUBUNTU-CVE-2026-98796
Ubuntu:24.04:LTSlinux-azure-6.14no fix listedUBUNTU-CVE-2026-98796
Ubuntu:24.04:LTSlinux-azure-6.17no fix listedUBUNTU-CVE-2026-98796
Ubuntu:22.04:LTSlinux-azure-6.2no fix listedUBUNTU-CVE-2026-98796
Ubuntu:22.04:LTSlinux-azure-6.5no fix listedUBUNTU-CVE-2026-98796
Ubuntu:22.04:LTSlinux-azure-6.8no fix listedUBUNTU-CVE-2026-98796
Ubuntu:24.04:LTSlinux-azure-7.0no fix listedUBUNTU-CVE-2026-98796
Ubuntu:22.04:LTSlinux-azure-fdeno fix listedUBUNTU-CVE-2026-98796
Ubuntu:24.04:LTSlinux-azure-fdeno fix listedUBUNTU-CVE-2026-98796
Ubuntu:26.04:LTSlinux-azure-fdeno fix listedUBUNTU-CVE-2026-98796
Ubuntu:22.04:LTSlinux-azure-fde-5.19no fix listedUBUNTU-CVE-2026-98796
Ubuntu:24.04:LTSlinux-azure-fde-6.14no fix listedUBUNTU-CVE-2026-98796
Ubuntu:24.04:LTSlinux-azure-fde-6.17no fix listedUBUNTU-CVE-2026-98796
Ubuntu:22.04:LTSlinux-azure-fde-6.2no fix listedUBUNTU-CVE-2026-98796
Ubuntu:22.04:LTSlinux-azure-fde-6.8no fix listedUBUNTU-CVE-2026-98796
Ubuntu:24.04:LTSlinux-azure-fde-7.0no fix listedUBUNTU-CVE-2026-98796
Ubuntu:24.04:LTSlinux-azure-nvidiano fix listedUBUNTU-CVE-2026-98796
Ubuntu:24.04:LTSlinux-azure-nvidia-6.14no fix listedUBUNTU-CVE-2026-98796
Ubuntu:22.04:LTSlinux-gcpno fix listedUBUNTU-CVE-2026-98796
Ubuntu:24.04:LTSlinux-gcpno fix listedUBUNTU-CVE-2026-98796
Ubuntu:26.04:LTSlinux-gcpno fix listedUBUNTU-CVE-2026-98796
Ubuntu:22.04:LTSlinux-gcp-5.19no fix listedUBUNTU-CVE-2026-98796
Ubuntu:24.04:LTSlinux-gcp-6.11no fix listedUBUNTU-CVE-2026-98796
Ubuntu:24.04:LTSlinux-gcp-6.14no fix listedUBUNTU-CVE-2026-98796
Ubuntu:24.04:LTSlinux-gcp-6.17no fix listedUBUNTU-CVE-2026-98796
Ubuntu:22.04:LTSlinux-gcp-6.2no fix listedUBUNTU-CVE-2026-98796
Ubuntu:22.04:LTSlinux-gcp-6.5no fix listedUBUNTU-CVE-2026-98796
Ubuntu:22.04:LTSlinux-gcp-6.8no fix listedUBUNTU-CVE-2026-98796
Ubuntu:24.04:LTSlinux-gcp-7.0no fix listedUBUNTU-CVE-2026-98796
Ubuntu:22.04:LTSlinux-gkeno fix listedUBUNTU-CVE-2026-98796
Ubuntu:24.04:LTSlinux-gkeno fix listedUBUNTU-CVE-2026-98796
Ubuntu:26.04:LTSlinux-gkeno fix listedUBUNTU-CVE-2026-98796
Ubuntu:22.04:LTSlinux-gkeopno fix listedUBUNTU-CVE-2026-98796
Ubuntu:24.04:LTSlinux-gkeopno fix listedUBUNTU-CVE-2026-98796
Ubuntu:22.04:LTSlinux-hwe-5.19no fix listedUBUNTU-CVE-2026-98796
Ubuntu:24.04:LTSlinux-hwe-6.11no fix listedUBUNTU-CVE-2026-98796
Ubuntu:24.04:LTSlinux-hwe-6.14no fix listedUBUNTU-CVE-2026-98796
Ubuntu:24.04:LTSlinux-hwe-6.17no fix listedUBUNTU-CVE-2026-98796
Ubuntu:22.04:LTSlinux-hwe-6.2no fix listedUBUNTU-CVE-2026-98796
Ubuntu:22.04:LTSlinux-hwe-6.5no fix listedUBUNTU-CVE-2026-98796
Ubuntu:22.04:LTSlinux-hwe-6.8no fix listedUBUNTU-CVE-2026-98796
Ubuntu:24.04:LTSlinux-hwe-7.0no fix listedUBUNTU-CVE-2026-98796
Ubuntu:22.04:LTSlinux-ibmno fix listedUBUNTU-CVE-2026-98796
Ubuntu:24.04:LTSlinux-ibmno fix listedUBUNTU-CVE-2026-98796
Ubuntu:26.04:LTSlinux-ibmno fix listedUBUNTU-CVE-2026-98796
Ubuntu:22.04:LTSlinux-ibm-6.8no fix listedUBUNTU-CVE-2026-98796
Ubuntu:22.04:LTSlinux-intel-iot-realtimeno fix listedUBUNTU-CVE-2026-98796
Ubuntu:22.04:LTSlinux-intel-iotgno fix listedUBUNTU-CVE-2026-98796
Ubuntu:22.04:LTSlinux-kvmno fix listedUBUNTU-CVE-2026-98796
Ubuntu:22.04:LTSlinux-lowlatencyno fix listedUBUNTU-CVE-2026-98796
Ubuntu:24.04:LTSlinux-lowlatencyno fix listedUBUNTU-CVE-2026-98796
Ubuntu:22.04:LTSlinux-lowlatency-hwe-5.19no fix listedUBUNTU-CVE-2026-98796
Ubuntu:24.04:LTSlinux-lowlatency-hwe-6.11no fix listedUBUNTU-CVE-2026-98796
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.2no fix listedUBUNTU-CVE-2026-98796
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.5no fix listedUBUNTU-CVE-2026-98796
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.8no fix listedUBUNTU-CVE-2026-98796
Ubuntu:22.04:LTSlinux-nvidiano fix listedUBUNTU-CVE-2026-98796
Ubuntu:24.04:LTSlinux-nvidiano fix listedUBUNTU-CVE-2026-98796
Ubuntu:26.04:LTSlinux-nvidiano fix listedUBUNTU-CVE-2026-98796
Ubuntu:24.04:LTSlinux-nvidia-6.11no fix listedUBUNTU-CVE-2026-98796
Ubuntu:24.04:LTSlinux-nvidia-6.17no fix listedUBUNTU-CVE-2026-98796
Ubuntu:22.04:LTSlinux-nvidia-6.2no fix listedUBUNTU-CVE-2026-98796
Ubuntu:22.04:LTSlinux-nvidia-6.5no fix listedUBUNTU-CVE-2026-98796
Ubuntu:22.04:LTSlinux-nvidia-6.8no fix listedUBUNTU-CVE-2026-98796
Ubuntu:24.04:LTSlinux-nvidia-7.0no fix listedUBUNTU-CVE-2026-98796
Ubuntu:26.04:LTSlinux-nvidia-bosno fix listedUBUNTU-CVE-2026-98796
Ubuntu:24.04:LTSlinux-nvidia-lowlatencyno fix listedUBUNTU-CVE-2026-98796
Ubuntu:22.04:LTSlinux-nvidia-tegrano fix listedUBUNTU-CVE-2026-98796
Ubuntu:24.04:LTSlinux-nvidia-tegrano fix listedUBUNTU-CVE-2026-98796
Ubuntu:22.04:LTSlinux-nvidia-tegra-igxno fix listedUBUNTU-CVE-2026-98796
Ubuntu:22.04:LTSlinux-oem-5.17no fix listedUBUNTU-CVE-2026-98796
Ubuntu:22.04:LTSlinux-oem-6.0no fix listedUBUNTU-CVE-2026-98796
Ubuntu:22.04:LTSlinux-oem-6.1no fix listedUBUNTU-CVE-2026-98796
Ubuntu:24.04:LTSlinux-oem-6.11no fix listedUBUNTU-CVE-2026-98796
Ubuntu:24.04:LTSlinux-oem-6.14no fix listedUBUNTU-CVE-2026-98796
Ubuntu:24.04:LTSlinux-oem-6.17no fix listedUBUNTU-CVE-2026-98796
Ubuntu:22.04:LTSlinux-oem-6.5no fix listedUBUNTU-CVE-2026-98796
Ubuntu:24.04:LTSlinux-oem-6.8no fix listedUBUNTU-CVE-2026-98796
Ubuntu:26.04:LTSlinux-oem-7.0no fix listedUBUNTU-CVE-2026-98796
Ubuntu:22.04:LTSlinux-oracleno fix listedUBUNTU-CVE-2026-98796
Ubuntu:24.04:LTSlinux-oracleno fix listedUBUNTU-CVE-2026-98796
Ubuntu:26.04:LTSlinux-oracleno fix listedUBUNTU-CVE-2026-98796
Ubuntu:24.04:LTSlinux-oracle-6.14no fix listedUBUNTU-CVE-2026-98796
Ubuntu:24.04:LTSlinux-oracle-6.17no fix listedUBUNTU-CVE-2026-98796
Ubuntu:22.04:LTSlinux-oracle-6.5no fix listedUBUNTU-CVE-2026-98796
Ubuntu:22.04:LTSlinux-oracle-6.8no fix listedUBUNTU-CVE-2026-98796
Ubuntu:24.04:LTSlinux-oracle-7.0no fix listedUBUNTU-CVE-2026-98796
Ubuntu:22.04:LTSlinux-raspino fix listedUBUNTU-CVE-2026-98796
Ubuntu:24.04:LTSlinux-raspino fix listedUBUNTU-CVE-2026-98796
Ubuntu:26.04:LTSlinux-raspino fix listedUBUNTU-CVE-2026-98796
Ubuntu:24.04:LTSlinux-raspi-realtimeno fix listedUBUNTU-CVE-2026-98796
Ubuntu:22.04:LTSlinux-realtimeno fix listedUBUNTU-CVE-2026-98796
Ubuntu:24.04:LTSlinux-realtimeno fix listedUBUNTU-CVE-2026-98796
Ubuntu:26.04:LTSlinux-realtimeno fix listedUBUNTU-CVE-2026-98796
Ubuntu:22.04:LTSlinux-riscvno fix listedUBUNTU-CVE-2026-98796
Ubuntu:24.04:LTSlinux-riscvno fix listedUBUNTU-CVE-2026-98796
Ubuntu:26.04:LTSlinux-riscvno fix listedUBUNTU-CVE-2026-98796
Ubuntu:22.04:LTSlinux-riscv-5.19no fix listedUBUNTU-CVE-2026-98796
Ubuntu:24.04:LTSlinux-riscv-6.14no fix listedUBUNTU-CVE-2026-98796
Ubuntu:24.04:LTSlinux-riscv-6.17no fix listedUBUNTU-CVE-2026-98796
Ubuntu:22.04:LTSlinux-riscv-6.5no fix listedUBUNTU-CVE-2026-98796
Ubuntu:22.04:LTSlinux-riscv-6.8no fix listedUBUNTU-CVE-2026-98796
Ubuntu:24.04:LTSlinux-riscv-7.0no fix listedUBUNTU-CVE-2026-98796
Ubuntu:22.04:LTSlinux-starfive-5.19no fix listedUBUNTU-CVE-2026-98796
Ubuntu:22.04:LTSlinux-starfive-6.2no fix listedUBUNTU-CVE-2026-98796
Ubuntu:22.04:LTSlinux-starfive-6.5no fix listedUBUNTU-CVE-2026-98796
Ubuntu:24.04:LTSlinux-vmwareno fix listedUBUNTU-CVE-2026-98796
Ubuntu:24.04:LTSlinux-xilinxno fix listedUBUNTU-CVE-2026-98796
Ubuntu:22.04:LTSlinux-xilinx-zynqmpno fix listedUBUNTU-CVE-2026-98796

Affected products (as reported)

VendorProductVersions
Linux Linux 656e705243fd0c2864b89634ea16ed444ef64dc6 – before efc91ab1d97bd991faf50baa0ead35029f341eb9656e705243fd0c2864b89634ea16ed444ef64dc6 – before 42001839e425b2564b7297be579073a13a8fddf6656e705243fd0c2864b89634ea16ed444ef64dc6 – before 82be3d08de9e14d5aed72377f051adb4f09fd540656e705243fd0c2864b89634ea16ed444ef64dc6 – before 17eafd74de5a31e30361420a2e3ebf64186b77e5656e705243fd0c2864b89634ea16ed444ef64dc6 – before 6f0c2c4f5e7143eba75153ecc8af3a03f7b6a98b
Linux Linux 4.6

References