Vulnerability in phy: qcom-qmp package - Fix Reset-Controller Leak on Probe Errors
Summary
GSD-2022-1003882: phy: qcom-qmp: fix reset-controller leak on probe errors. Affects Kernel versions >= e78f3d15e115e8e764d4b1562b4fa538f2e22f6b, < a39d9eccb333b8c07c43ebea1c6dfda122378a0f. 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 phy: qcom-qmp package is a component of the Linux Kernel, specifically designed for Qualcomm's QMP (Qualcomm Message Parser) PHY (Physical Layer) driver. It provides functionality for managing and controlling the reset-controller in Qualcomm's QMP PHY. The reset-controller is responsible for resetting various hardware components in the system. This package is vulnerable to a specific issue related to probe errors, which can lead to a resource leak in the reset-controller.
Vulnerability Detail
The vulnerability in the phy: qcom-qmp package occurs when there are probe errors during the initialization process. In such cases, the reset-controller is not properly released, resulting in a resource leak. This can have various ramifications, including potential memory leaks and resource exhaustion. 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 was introduced in version v4.12 of the Linux Kernel and has been fixed in version v4.19.247.
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 vulnerability in the phy: qcom-qmp package can lead to resource leaks and potential security risks. To mitigate this vulnerability, it is crucial to update the Linux Kernel to version v4.19.247 or later. For further support on vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
The vulnerability can potentially lead to memory leaks and resource exhaustion. It may also allow an attacker to cause a denial-of-service condition or execute arbitrary code with elevated privileges.
You can use Vulert's playground at Vulert Scanner to check if your system is affected by this vulnerability. Vulert monitors and alerts in real-time for open-source vulnerabilities, using just a manifest file like package-lock.json.
No specific workaround has been provided for this vulnerability. It is recommended to update the Linux Kernel to the fixed version.
The exact exploitability of this vulnerability depends on various factors, including the system configuration and network setup. However, in general, an attacker would need local access to the system to exploit this vulnerability.
There are no known instances of this vulnerability being exploited in the wild. However, it is always recommended to apply security updates promptly to mitigate potential risks.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
