CVE-2026-43260: bnxt_en: Fix RSS context delete logic
In the Linux kernel, the following vulnerability has been resolved:
bnxten: 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 netifrunning() 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, netifrunning() check is not necessary.
Remove the netifrunning() condition check when deleting an RSS context.
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2026-43260?
CVE-2026-43260 has a severity rating that varies based on its impact on the Linux kernel and specific configurations.
How do I fix CVE-2026-43260?
To fix CVE-2026-43260, you should update your Linux kernel to the latest stable version that includes the patch for this vulnerability.
Which versions of the Linux kernel are affected by CVE-2026-43260?
CVE-2026-43260 affects multiple versions of the Linux kernel including those between 6.11 and 6.12.75, 6.13 and 6.18.16, 6.19 and 6.19.6, and also 7.0-rc1.
What component is involved in CVE-2026-43260?
The component involved in CVE-2026-43260 is the bnxt_en driver in the Linux kernel.
What type of attack can CVE-2026-43260 lead to?
CVE-2026-43260 can potentially lead to issues with RSS context management, which may affect network performance and stability.