dpaa2-switch: fix handling of NAPI on the remove path
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 0b1b71370458860579831e77485883fcf2e8fbbe · < e23d7c8c1d4ba435c457d7ffb2669175ec819b07| No fix yet |
| Linux Linux |
|
|
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.
From the CVE record · Linux
The dpaa2-switch removal path can delete shared NAPI instances before they are disabled as switch ports are unregistered and freed. The input does not describe an attacker action or specify access, authentication, or user-interaction conditions.
Engineers running Linux kernels with dpaa2-switch support should check their affected versions; none are listed in the input.