Vulnerability in Kernel package: scsi: bnx2fc: Make bnx2fc_recv_frame() mp safe
Summary
GSD-2022-1000176: scsi: bnx2fc: Make bnx2fc_recv_frame() mp safe. Affects Kernel versions >= d576a5e80cd07ea7049f8fd7b303c14df7b5d7d2, < 53e4f71763c61a557283eb43301efd671922d1e8. 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 Kernel package is a crucial component of the Linux operating system, responsible for managing the system's core functionality. It provides an interface between the hardware and software layers, allowing applications to communicate with the underlying hardware. The scsi subsystem within the Kernel package handles storage devices, including Fibre Channel (FC) adapters. The bnx2fc module is a driver for Broadcom NetXtreme II FC HBA devices. This vulnerability specifically affects the bnx2fc_recv_frame() function within the bnx2fc module.
Vulnerability Detail
The bnx2fc_recv_frame() function in the bnx2fc module of the Kernel package is not multi-processor (mp) safe. This vulnerability can potentially lead to race conditions and other concurrency issues when multiple processors attempt to access the function simultaneously. An attacker could exploit these issues to cause a denial-of-service (DoS) condition, escalate privileges, or execute arbitrary code. The vulnerability was introduced in version v3.16 of the Linux Kernel and has been fixed in version v5.4.178.
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 known workaround for this vulnerability. It is essential to apply the fix by updating the Kernel package to a version that includes the necessary patch.
Conclusion
The vulnerability in the bnx2fc_recv_frame() function of the Kernel package can lead to various security risks, including denial-of-service, privilege escalation, and arbitrary code execution. It is crucial to update the Kernel package to version v5.4.178 or later to mitigate these risks. For further assistance or support in vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
This vulnerability can potentially lead to a denial-of-service (DoS) condition, privilege escalation, or arbitrary code execution.
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 Vulert will analyze it for any known vulnerabilities.
At the time of this report, there is no known public exploit for this vulnerability. However, it is crucial to apply the fix as soon as possible to mitigate any potential risks.
This vulnerability requires local access to the system. An attacker would need to have the ability to execute arbitrary code or escalate privileges on the affected system.
To exploit this vulnerability, an attacker would need to have local access to the system and the ability to execute arbitrary code or escalate privileges.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
