CVE-2026-97434 json
dpaa2-switch: fix handling of NAPI on the remove path
published 2026-09-24 45 d ago modified 2026-10-03 37 d ago also EUVD-2026-86047
- cvss
- —
- not scored
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 6%
- public exploits
- 0
- none known
Summary
In the Linux kernel, the following vulnerability has been resolved:
dpaa2-switch: fix handling of NAPI on the remove path
All the NAPI instances for a DPSW device are attached to the first switch port's net_device but shared by all ports. The NAPI instances get disabled only once the last port goes down.
This causes an issue on the .remove() path where each port is unregistered and freed one at a time, causing the NAPI instances to be deleted even though they are not disabled.
In order to avoid this, split up the unregister_netdev() calls from the free_netdev() so that we make sure all ports go down before we attempt a deletion of NAPI instances. Also, make the netif_napi_del() explicit as it is on the .probe() path.
Patch / fix
- Linux Linux 5.15.222, 6.1.189, 6.6.158, 6.12.111, 6.18.53, 7.2
- linux Debian 12 6.1.190-1
- linux Debian 13 6.12.111-1
- linux Debian 14 7.2.6-1
- linux-6.12 Debian 12 6.12.111-1~deb12u1
debian advisories DEBIAN-CVE-2026-97434
- linux Ubuntu 22.04 LTS 5.15.0-202.212
- linux Ubuntu 26.04 LTS 7.0.0-42.42
- linux-aws Ubuntu 22.04 LTS 5.15.0-1119.126
- linux-aws Ubuntu 26.04 LTS 7.0.0-1016.17
- linux-gcp Ubuntu 22.04 LTS 5.15.0-1120.130
- linux-gcp Ubuntu 26.04 LTS 7.0.0-1016.18
- linux-gke Ubuntu 22.04 LTS 5.15.0-1115.121
- linux-ibm Ubuntu 22.04 LTS 5.15.0-1113.117
ubuntu advisories UBUNTU-CVE-2026-97434
Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
- git.kernel.org/stable/c/d39603e21087e9ef9cd125e5895cdc70b2eb154d commit
- git.kernel.org/stable/c/bd16f46d0796109d241d6311a7577f9956467c96 commit
- git.kernel.org/stable/c/c996faba71fc465ad12c6d177bd1a9ad974f9ee8 commit
- git.kernel.org/stable/c/569df157eb874cb3b50554d73b89f31599397b42 commit
- git.kernel.org/stable/c/6518f87771c8833e587bd9881346fa759651c2ae commit
- git.kernel.org/stable/c/e23d7c8c1d4ba435c457d7ffb2669175ec819b07 commit
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2026-97434 updated cvss 5.5
kernel: dpaa2-switch: fix handling of NAPI on the remove path
-
Red Hat Enterprise Linux 10 kernelaffected: workaround, no fix available “Fix deferred”
-
Red Hat Enterprise Linux 6 perf, kernel, python-perf, kernel-kdump, kernel-firmware, kernel-bootwrapper, +1 more Red Hat Enterprise Linux 7 perf, kernel, bpftool, kernel-rt, python-perf, kernel-kdump, +8 more Red Hat Enterprise Linux 8 perf, kernel, bpftool, kernel-rt, kernel-core, kernel-tools, +29 more Red Hat Enterprise Linux 9 rv, perf, rtla, kernel, bpftool, libperf, +83 more Red Hat OpenShift Container Platform 4 openshift/ose-rhel-coreos-8, openshift/ose-rhel-coreos-9 Red Hat OpenShift Container Platform 5 openshift/ose-rhel-coreos-9not affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
0.17% chance of exploitation in the next 30 days, higher than 6% of all scored CVEs (FIRST EPSS, 2026-11-08).
Affected products
- Linux Linux
Classification
- Technology feeds
References
- git.kernel.org /stable/c/d39603e21087e9ef9cd125e5895cdc70b2eb154d
- git.kernel.org /stable/c/bd16f46d0796109d241d6311a7577f9956467c96
- git.kernel.org /stable/c/c996faba71fc465ad12c6d177bd1a9ad974f9ee8
- git.kernel.org /stable/c/569df157eb874cb3b50554d73b89f31599397b42
- git.kernel.org /stable/c/6518f87771c8833e587bd9881346fa759651c2ae
- git.kernel.org /stable/c/e23d7c8c1d4ba435c457d7ffb2669175ec819b07
Sources
- CVE List CVE-2026-97434
- NVD CVE-2026-97434
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.