s390/qeth: NULL dereference in qeth_clear_working_pool_list()
Summary
GSD-2021-1001670: s390/qeth: fix NULL deref in qeth_clear_working_pool_list(). Affects Kernel versions >= eff73e16ee116f6eafa2be48fab42659a27cb453, < db94f89e1dadf693c15c2d60de0c34777cea5779. 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 s390/qeth package is a component of the Linux Kernel that provides support for the IBM System z network devices. It includes drivers and utilities for managing and configuring these devices. The qeth_clear_working_pool_list() function is responsible for clearing the working pool list used by the qeth driver. This function is called during the shutdown process of the driver.
Vulnerability Detail
The vulnerability identified as GSD-2021-1001670 is a NULL dereference issue in the qeth_clear_working_pool_list() function. This vulnerability was introduced in version v5.9 of the Linux Kernel and fixed in version v5.10.70. The vulnerability occurs when the function is called with a NULL pointer, leading to a crash or potential privilege escalation. An attacker could potentially exploit this vulnerability to crash the system or execute arbitrary code with 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 essential to apply the provided fix by updating the Linux Kernel to the recommended version.
Conclusion
The NULL dereference vulnerability in the qeth_clear_working_pool_list() function of the s390/qeth package can lead to system crashes or potential privilege escalation. It is crucial to update the Linux Kernel to version v5.10.70 or later to mitigate 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 potential privilege escalation, allowing an attacker to execute arbitrary code with elevated privileges.
You can use the Vulert Playground at Vulert Scanner to check if your system is affected by this vulnerability. Simply upload your package-lock.json file to the playground, and it will provide real-time alerts for open-source vulnerabilities, including this one.
At the time of this report, there is no known exploit for this vulnerability. However, it is crucial to apply the recommended fix to mitigate any potential risks.
This vulnerability requires local access to the system to exploit. However, if an attacker gains local access, they can potentially exploit this vulnerability to crash the system or execute arbitrary code with elevated privileges.
The recommended solution is to update the Linux Kernel to the fixed version. There are no known alternative solutions or workarounds for this vulnerability.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
