net/qla3xxx: Fix schedule while atomic in ql_sem_spinlock
Summary
GSD-2021-1001014: net/qla3xxx: fix schedule while atomic in ql_sem_spinlock. Affects Kernel versions < 2ed296c47e5c545a26bb774ec7a87e5369e6ddf9. 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 net/qla3xxx package is a part of the Linux Kernel ecosystem. It provides support for QLogic Fibre Channel Host Bus Adapters (HBAs) based on the ISP23xx and ISP24xx chipsets. These HBAs are commonly used for connecting servers to storage devices in data centers. The ql_sem_spinlock function in the qla3xxx driver is responsible for acquiring and releasing a spinlock to protect critical sections of code. However, a vulnerability has been discovered in this function that allows a schedule while atomic condition, which can lead to a system crash or other unexpected behavior.
Vulnerability Detail
The vulnerability in the ql_sem_spinlock function arises from a schedule while atomic condition. This occurs when the function attempts to sleep while holding a spinlock, which is not allowed in atomic contexts. This can lead to a system crash or other unpredictable behavior. An attacker may be able to exploit this vulnerability to cause a denial-of-service condition or potentially execute arbitrary code with elevated privileges. The vulnerability has been fixed in Linux Kernel version v5.12.11 by commit 2ed296c47e5c545a26bb774ec7a87e5369e6ddf9.
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 →
Conclusion
The net/qla3xxx package in the Linux Kernel is vulnerable to a schedule while atomic condition in the ql_sem_spinlock function. This can lead to system crashes or other unexpected behavior. It is recommended to update the Linux Kernel to version v5.12.11 or later to fix this vulnerability. For further support on vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
The vulnerability can lead to a system crash or other unexpected behavior, potentially causing a denial-of-service condition or enabling an attacker to execute arbitrary code 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 known vulnerabilities.
No, there is no known workaround for this vulnerability. It is recommended to update the Linux Kernel to the fixed version.
There are no known exploits for this vulnerability at the time of this report. However, it is important to apply the fix as soon as possible to mitigate any potential risks.
More information about the fix can be found in the commit 2ed296c47e5c545a26bb774ec7a87e5369e6ddf9 in the Linux Kernel source code repository.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
