net/qla3xxx: Fix schedule while atomic in ql_sem_spinlock
Summary
GSD-2021-1000871: net/qla3xxx: fix schedule while atomic in ql_sem_spinlock. Affects Kernel versions < 92473994deec84b46ba98700810f2a025a30a9e1. 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) using the qla3xxx driver. These HBAs are commonly used in enterprise storage systems. 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 exists in this function that allows a schedule while atomic condition to occur, leading to potential system instability and crashes.
Vulnerability Detail
The vulnerability in the ql_sem_spinlock function arises from a schedule while atomic condition. This occurs when the function is called in an atomic context, such as within an interrupt handler, and attempts to perform a blocking operation that may cause the calling thread to sleep. This can lead to a deadlock or other system instability. An attacker with local access to the system may be able to trigger this vulnerability to disrupt system operation or potentially gain elevated privileges.
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 recommended to apply the fix by updating the Linux Kernel as mentioned in the 'how_to_fix' section.
Conclusion
The net/qla3xxx package in the Linux Kernel is vulnerable to a schedule while atomic condition in the ql_sem_spinlock function. This vulnerability can lead to system instability and crashes, potentially allowing an attacker with local access to the system to gain elevated privileges. It is recommended to update the Linux Kernel to version v4.19.195 or later to fix this vulnerability. For further support on vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
This vulnerability can lead to system instability and crashes, potentially disrupting normal system operation and causing denial-of-service conditions. In some cases, an attacker with local access to the system may be able to exploit this vulnerability to gain elevated privileges.
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 and Vulert will analyze it for any open-source vulnerabilities, including this one.
Yes, a patch for this vulnerability has been released in the Linux Kernel version v4.19.195. Users are advised to update their Linux Kernel to this version or later to fix the vulnerability.
No, this vulnerability requires local access to the system in order to be exploited.
There are no known instances of this vulnerability being exploited in the wild at the time of this report.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
