Vulnerability in bnxt_en package: Fix RX consumer index logic in the error path
Summary
GSD-2021-1000420: bnxt_en: Fix RX consumer index logic in the error path. Affects Kernel versions >= a1b0e4e684e9c300b9e759b46cb7a0147e61ddff, < b1523e4ba293b2a32d9fabaf70c1dcaa6e3e2847. 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 adapters. It is a part of the Linux Kernel ecosystem. This package provides support for various Broadcom Ethernet adapters, enabling communication between the operating system and the network hardware. The vulnerability in question affects the RX consumer index logic in the error path of the bnxt_en package.
Vulnerability Detail
The vulnerability arises from a flaw in the RX consumer index logic within the error path of 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 with elevated privileges. The impact and attack plausibility of this vulnerability have not been proven yet. The vulnerability was introduced in version v5.1 of the Linux Kernel and has been fixed in version v5.4.119 by commit b1523e4ba293b2a32d9fabaf70c1dcaa6e3e2847.
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
The vulnerability in the bnxt_en package's RX consumer index logic within the error path can lead to a denial-of-service condition or arbitrary code execution. It is crucial to update the Linux Kernel to version v5.4.119 or later to mitigate this vulnerability. For further support on vulnerability remediation, you can reach out to DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
The impact of this vulnerability can range from a denial-of-service (DoS) condition to arbitrary code execution with elevated privileges.
You can use the Vulert Playground (https://vulert.com/scanner) to check if your system is affected by this vulnerability. Simply upload your package-lock.json file and the Vulert Playground will analyze it for any open-source vulnerabilities, including this one.
As of now, there is no known exploit for this vulnerability. However, it is important to apply the recommended fix to mitigate any potential risks.
Yes, this vulnerability can be exploited remotely if the affected system is accessible over the network.
The recommended solution is to update the Linux Kernel to the fixed version. However, if updating is not feasible, you can consider implementing additional security measures, such as network segmentation and access controls, to reduce the risk of exploitation.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
