Null Return Check Vulnerability in soc: qcom: rpmpd
Summary
GSD-2022-1002264: soc: qcom: rpmpd: Check for null return of devm_kcalloc. Affects Kernel versions >= bbe3a66c3f5a65fb3d702351bac2a6033944d389, < 755dbc3d73789ac9f0017c729abf5e4b153bf799. 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 fails to check for a null return. 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 has been fixed in version v5.4.189. The vulnerability could potentially be exploited to execute arbitrary code or cause a denial of service.
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 lead to security issues. It is recommended to update the Linux Kernel to the fixed version to mitigate this vulnerability. For further support on vulnerability remediation, you can 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 and provides power management functionality for Qualcomm processors.
The impact of this vulnerability is not yet proven, but it could potentially allow an attacker to execute arbitrary code or cause a denial of service.
To fix this vulnerability, it is recommended to update the Linux Kernel to version v5.4.189 or later.
No specific workaround has been mentioned for this vulnerability.
For more information about this vulnerability, you can refer to the source link provided in the database_specific section of the vulnerability details.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
