Fix error handling in a4xx_gpu_init() in drm/msm/a4xx
Summary
GSD-2021-1001898: drm/msm/a4xx: fix error handling in a4xx_gpu_init(). Affects Kernel versions >= 5785dd7a8ef0de8049f40a1a109de6a1bf17b479, < 3962d626eb3e3b23ebb2e2a61537fa764acbfe11. 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 drm/msm/a4xx package is a component of the Linux Kernel that provides support for the Adreno 4xx series of GPUs. These GPUs are commonly found in Qualcomm Snapdragon processors and are used in various mobile devices. The a4xx_gpu_init() function is responsible for initializing the GPU and its associated resources during the device boot process.
Vulnerability Detail
The vulnerability identified in drm/msm/a4xx is related to error handling in the a4xx_gpu_init() function. The issue was introduced in Linux Kernel version v5.11 and was fixed in version v5.14.14. The vulnerability could potentially be exploited by an attacker to cause a denial-of-service (DoS) condition or execute arbitrary code with kernel privileges. The specific technical details of the vulnerability have not been disclosed.
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
No workaround has been provided for this vulnerability.
Conclusion
The vulnerability in drm/msm/a4xx's a4xx_gpu_init() function can potentially lead to a denial-of-service (DoS) condition or arbitrary code execution with kernel privileges. It is crucial to update the Linux Kernel to version v5.14.14 or later to mitigate this vulnerability. For further support on vulnerability remediation, you can reach out to DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
The impact of this vulnerability could range from a denial-of-service (DoS) condition to the execution of arbitrary code with kernel privileges. The specific consequences depend on the nature of the vulnerability and the attacker's capabilities.
You can use the Vulert 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 known vulnerabilities, including this one.
No known exploits for this vulnerability have been disclosed at the time of this report. However, it is always recommended to apply security patches promptly to mitigate the risk of potential exploits.
The exact details of the vulnerability have not been disclosed, so it is difficult to determine if it can be exploited remotely. However, given that it affects the kernel, it is possible that remote exploitation may be feasible in certain scenarios.
For more details about this vulnerability, you can refer to the source information provided by the Cloud Security Alliance's GSD database (https://github.com/cloudsecurityalliance/gsd-database/blob/main/2021/1001xxx/GSD-2021-1001898.json).
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
