Vulnerability in bnxt_en package: Fix RX consumer index logic in the error path
Summary
GSD-2021-1000230: bnxt_en: Fix RX consumer index logic in the error path. Affects Kernel versions >= a1b0e4e684e9c300b9e759b46cb7a0147e61ddff, < 3fbc5bc651d688fbea2a59cdc91520a2f5334d0a. No fix is published. How to fix ↓
Check if this vulnerability affects your application
Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.
No signup required · Results in about 60 seconds
Background
The bnxt_en package is a network driver for Broadcom NetXtreme Ethernet devices in the Linux Kernel. It provides support for various Broadcom network adapters. The vulnerability in question relates to the RX consumer index logic in the error path of the package.
Vulnerability Detail
The vulnerability arises from a flaw in the RX consumer index logic within the bnxt_en package. This flaw can potentially be exploited by an attacker to cause a denial-of-service (DoS) condition or execute arbitrary code. The vulnerability was introduced in version v5.1 of the Linux Kernel and has been fixed in version v5.12.4. For more technical details, please refer to the references provided.
How To Fix
No fixed version is published for this vulnerability.
Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →
Workaround
There is no specific workaround mentioned for this vulnerability.
Conclusion
In conclusion, the bnxt_en package in the Linux Kernel is vulnerable to a flaw in the RX consumer index logic. This vulnerability can potentially result in a denial-of-service condition or arbitrary code execution. It is recommended to update to Linux Kernel version v5.12.4 or later to mitigate this vulnerability. For further support on vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
The vulnerability can potentially lead to a denial-of-service (DoS) condition or allow an attacker to execute arbitrary code.
You can use the Vulert Playground at Vulert Scanner to check if your system is affected by this vulnerability. Simply upload your package-lock.json file and the tool will provide real-time alerts for any open-source vulnerabilities.
Yes, the vulnerability has been fixed in Linux Kernel version v5.12.4. It is recommended to update to this version or a later one to address the issue.
Yes, this vulnerability can be exploited remotely if the affected system is accessible over the network.
There are no known instances of this vulnerability being exploited in the wild at the time of this report.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
