Vulnerability in Kernel package: scsi: bnx2fc: Make bnx2fc_recv_frame() mp safe
Summary
GSD-2022-1000092: scsi: bnx2fc: Make bnx2fc_recv_frame() mp safe. Affects Kernel versions >= d576a5e80cd07ea7049f8fd7b303c14df7b5d7d2, < 3a345198a7c2d1db2526dc60b77052f75de019d3. 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 critical component of the Linux operating system, responsible for managing the system's core functionality. It provides the necessary interfaces and drivers for hardware devices, including storage devices. The scsi (Small Computer System Interface) subsystem within the Kernel handles communication with SCSI devices, such as disk drives. One of the components within the scsi subsystem is bnx2fc, which is responsible for handling Fibre Channel over Ethernet (FCoE) traffic for Broadcom NetXtreme II devices. This vulnerability specifically affects the bnx2fc_recv_frame() function within the bnx2fc component.
Vulnerability Detail
The bnx2fc_recv_frame() function in the bnx2fc component of the Kernel is not multi-processor (mp) safe. This means that concurrent execution of this function by multiple processors can lead to race conditions and potential security vulnerabilities. Attackers may be able to exploit these race conditions to gain unauthorized access, execute arbitrary code, or cause denial-of-service (DoS) conditions. The impact and attack plausibility of this vulnerability have not been proven yet.
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 Kernel package's bnx2fc component can potentially lead to security risks if left unaddressed. It is crucial to update the Linux Kernel to version v4.9.300 or later to fix this vulnerability. For further support and assistance in vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
The impact of this vulnerability is not yet proven, but it could potentially allow attackers to gain unauthorized access, execute arbitrary code, or cause denial-of-service conditions.
You can use Vulert's playground (https://vulert.com/scanner) to check if your system is affected by this vulnerability. Simply upload your package-lock.json file to the playground, and it will alert you in real-time if your application is affected.
There is currently no known exploit for this vulnerability. However, it is still important to update the Kernel to the fixed version to mitigate any potential risks.
There is no specific temporary measure mentioned for this vulnerability. It is recommended to update the Kernel as soon as possible.
You can find more information about this vulnerability in the GSD-2022-1000092.json file in the GSD database (https://github.com/cloudsecurityalliance/gsd-database).
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
