Vulnerability in drm/msm/a6xx Package: Refcount Leak in a6xx_gpu_init
Summary
GSD-2022-1003601: drm/msm/a6xx: Fix refcount leak in a6xx_gpu_init. Affects Kernel versions >= 4b565ca5a2cbbbb6345e8789da89c193b6b00e5a, < 48e82ce8cdb19c20a5020fa446b286d6a147450c. 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/a6xx package is a component of the Linux Kernel, specifically designed for the Adreno 6xx series of GPUs. It provides the necessary drivers and functionality for these GPUs to operate correctly. The a6xx_gpu_init function within this package is responsible for initializing the GPU and managing its resources. However, a vulnerability has been identified in this function that leads to a refcount leak, potentially causing resource exhaustion and other security issues.
Vulnerability Detail
The vulnerability in drm/msm/a6xx arises from a refcount leak in the a6xx_gpu_init function. This leak occurs when the function fails to properly release resources in certain error scenarios, leading to a gradual accumulation of unreleased resources. An attacker could potentially exploit this vulnerability to exhaust system resources, resulting in a denial-of-service condition or other security implications. The impact and attack plausibility of this vulnerability have not been proven yet.
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 specific workaround has been provided for this vulnerability. It is advised to apply the recommended fix by updating the Linux Kernel to the latest version.
Conclusion
In conclusion, the vulnerability in drm/msm/a6xx's a6xx_gpu_init function poses a risk of resource exhaustion and potential denial-of-service conditions. It is crucial to update the Linux Kernel to version v5.10.121 or later to mitigate this vulnerability. No known exploits have been reported, but it is still important to apply the recommended fix to ensure system security. For more information and assistance, please contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
The impact of this vulnerability could potentially lead to resource exhaustion and denial-of-service conditions. However, the actual impact and attack plausibility have not been proven yet.
You can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability. Vulert monitors and alerts in real-time for open-source vulnerabilities without requiring access to the code or installation.
As of now, there is no known exploit for this vulnerability. However, it is still important to apply the recommended fix to ensure the security of your system.
While no specific workaround has been provided for this vulnerability, it is generally recommended to keep your system up to date with the latest security patches and follow best practices for system hardening.
You can find more information about this vulnerability in the Open Source Vulnerability Database (OSVDB) entry with ID GSD-2022-1003601. For further support and assistance, you can contact info@devnack.com.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
