Vulnerability in Kernel: scsi: bnx2fc_recv_frame() mp safe
Summary
GSD-2022-1000115: scsi: bnx2fc: Make bnx2fc_recv_frame() mp safe. Affects Kernel versions >= d576a5e80cd07ea7049f8fd7b303c14df7b5d7d2, < 471085571f926a1fe6b1bed095638994dbf23990. 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 is a critical component of the Linux operating system that provides core functionalities and acts as an interface between hardware and software. It manages system resources, facilitates communication between different software components, and enables the execution of user programs. The scsi (Small Computer System Interface) subsystem within the Kernel handles storage devices and their interactions. One of the components in the scsi subsystem is bnx2fc, which is responsible for Fibre Channel over Ethernet (FCoE) operations. The bnx2fc_recv_frame() function in bnx2fc is used to receive frames from the network. However, this function has a vulnerability that can be exploited by attackers.
Vulnerability Detail
The vulnerability in bnx2fc_recv_frame() function allows for a potential security breach. Although the impact and attack plausibility have not been proven, the vulnerability could potentially lead to unauthorized access, data leakage, or denial of service. The vulnerability was introduced in version v3.16 of the Linux Kernel by commit d576a5e80cd07ea7049f8fd7b303c14df7b5d7d2 and has been fixed in version v4.14.265 by commit 471085571f926a1fe6b1bed095638994dbf23990.
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 bnx2fc_recv_frame() function of the Kernel's bnx2fc component can potentially lead to unauthorized access, data leakage, or denial of service. It is crucial to update the Linux Kernel to version v4.14.265 or later to mitigate this vulnerability. For further support on vulnerability remediation, you can contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
The impact of this vulnerability could potentially include unauthorized access, data leakage, or denial of service.
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.
At the time of this report, there is no known exploit for this vulnerability. However, it is important to apply the recommended fix to mitigate any potential risks.
While it is technically possible to manually patch the vulnerable code, it is strongly recommended to update to the fixed version of the Linux Kernel instead. Manually patching the code can be complex and error-prone, and it may introduce other issues or conflicts with future updates.
For more information about this vulnerability, you can refer to the source database entry at https://github.com/cloudsecurityalliance/gsd-database/blob/main/2022/1000xxx/GSD-2022-1000115.json.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
