Null Return Check Vulnerability in soc: qcom: rpmpd
Summary
GSD-2022-1002109: soc: qcom: rpmpd: Check for null return of devm_kcalloc. Affects Kernel versions >= bbe3a66c3f5a65fb3d702351bac2a6033944d389, < b5d6eba71997b6d661935d2b15094ac7f9f6132d. 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 soc: qcom: rpmpd package is a component of the Linux Kernel, which is responsible for managing the Qualcomm RPM power domain. It provides power management functionality for Qualcomm processors. The vulnerability in this package arises from a lack of null return check in the devm_kcalloc function.
Vulnerability Detail
The vulnerability occurs when the devm_kcalloc function in soc: qcom: rpmpd does not check for a null return value. This can lead to a potential security vulnerability, although the actual impact and attack plausibility have not been proven. The vulnerability was introduced in version v5.1 of the Linux Kernel and is fixed in version v5.10.110 by commit b5d6eba71997b6d661935d2b15094ac7f9f6132d. For more details, please refer to the references link.
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 null return check vulnerability in soc: qcom: rpmpd can potentially pose security risks. It is recommended to update the Linux Kernel to the fixed version to mitigate any potential vulnerabilities. For further support on vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
The soc: qcom: rpmpd package is a component of the Linux Kernel that manages the Qualcomm RPM power domain, providing power management functionality for Qualcomm processors.
The impact of this vulnerability is currently unknown, as the actual attack plausibility has not been proven. However, it is recommended to update to the fixed version to mitigate any potential risks.
To fix this vulnerability, update the Linux Kernel to version v5.10.110 or later by pulling the latest changes from the official Linux Kernel repository.
No specific workaround has been mentioned for this vulnerability.
For more information about this vulnerability, please refer to the provided references link.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
