CVE-2026-97434

dpaa2-switch: fix handling of NAPI on the remove path

N/A

Published: September 24, 2026 at 04:03 PM UTC

Updated: October 3, 2026 at 11:17 AM UTC

1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available

Start Free Sign In

Severity

N/A

Exploit prediction

EPSS 0.2%

Description

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

Linux Kernel · Linux

95%

5.13 ≤ v < 5.15.2225.13 ≤ v < 6.1.1895.13 ≤ v < 6.12.1115.13 ≤ v < 6.18.535.13 ≤ v < 6.6.1585.13 ≤ v < 7.20b1b71370458860579831e77485883fcf2e8fbbe5.13

Vendor states this is fixed in 569df157eb874cb3b50554d73b89f31599397b42 (fixed)

Vendor states this is fixed in 6518f87771c8833e587bd9881346fa759651c2ae (fixed)

Vendor states this is fixed in bd16f46d0796109d241d6311a7577f9956467c96 (fixed)

Vendor states this is fixed in c996faba71fc465ad12c6d177bd1a9ad974f9ee8 (fixed)

Vendor states this is fixed in d39603e21087e9ef9cd125e5895cdc70b2eb154d (fixed)

Vendor states this is fixed in e23d7c8c1d4ba435c457d7ffb2669175ec819b07 (fixed)

Vendor states this is fixed in 5.13 (unaffected)

Vendor states this is fixed in 5.15.222 (unaffected)

Vendor states this is fixed in 6.1.189 (unaffected)

Vendor states this is fixed in 6.12.111 (unaffected)

Vendor states this is fixed in 6.18.53 (unaffected)

Vendor states this is fixed in 6.6.158 (unaffected)