bnxt_en: Fix RSS context delete logic
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
bnxt_en: Fix RSS context delete logic
We need to free the corresponding RSS context VNIC in FW everytime an RSS context is deleted in driver. Commit 667ac333dbb7 added a check to delete the VNIC in FW only when netif_running() is true to help delete RSS contexts with interface down.
Having that condition will make the driver leak VNICs in FW whenever close() happens with active RSS contexts. On the subsequent open(), as part of RSS context restoration, we will end up trying to create extra VNICs for which we did not make any reservation. FW can fail this request, thereby making us lose active RSS contexts.
Suppose an RSS context is deleted already and we try to process a delete request again, then the HWRM functions will check for validity of the request and they simply return if the resource is already freed. So, even for delete-when-down cases, netif_running() check is not necessary.
Remove the netif_running() condition check when deleting an RSS context.
From the CVE record · Linux
The Linux kernel’s bnxt_en driver can leak firmware VNICs when an interface closes with active RSS contexts. On a subsequent open, firmware may reject requests to restore those contexts, causing them to be lost. The input does not describe an attacker, access requirements, or user interaction.
Engineers running Linux kernels with the bnxt_en driver should check their versions against the vendor advisory; affected versions are not specified.