Use After Free Vulnerability in drm/msm/disp/dpu1 Package
Summary
GSD-2022-1003795: drm/msm/disp/dpu1: set vbif hw config to NULL to avoid use after memory free during pm runtime resume. Affects Kernel versions >= 25fdd5933e4c0f5fe2ea5cd59994f8ac5fbe90ef, < ef10d0c68e8608848cd58fca2589685718426607. 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/disp/dpu1 package is a component of the Linux Kernel that handles display-related functionality for Qualcomm Adreno GPUs. It provides support for managing display pipelines, configuring hardware resources, and handling power management. The package is widely used in various devices running on the Linux operating system, including smartphones, tablets, and embedded systems. However, a vulnerability has been discovered in the package that could lead to a use after free issue during power management runtime resume.
Vulnerability Detail
The vulnerability in the drm/msm/disp/dpu1 package arises when the vbif (Video Buffer Interface) hardware configuration is not properly handled during power management runtime resume. Due to this flaw, there is a possibility of accessing the vbif hardware configuration after it has been freed from memory, leading to a use after free scenario. An attacker could potentially exploit this vulnerability to execute arbitrary code, escalate privileges, or cause a denial of service. 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
There is no specific workaround mentioned for this vulnerability.
Conclusion
The use after free vulnerability in the drm/msm/disp/dpu1 package of the Linux Kernel could potentially lead to security breaches, including arbitrary code execution, privilege escalation, or denial of service. It is crucial to update the Linux Kernel to version v5.4.198 or later to mitigate this vulnerability. Additionally, following best security practices and keeping systems up to date is recommended. For further support on vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
The impact of this vulnerability could range from arbitrary code execution to privilege escalation or denial of service, depending on the attacker's capabilities.
You can use the Vulert Playground at Vulert Scanner to check if your system is affected by this vulnerability. Simply upload your package-lock.json file to the playground, and it will provide real-time monitoring and alerts for open-source vulnerabilities, including this one.
No known exploits for this vulnerability have been reported at this time. However, it is always recommended to apply security patches and updates to mitigate potential risks.
The exact attack vector and remote exploitability of this vulnerability have not been determined yet. It is advisable to follow best security practices and keep systems up to date to minimize potential risks.
For further support on vulnerability remediation, you can reach out to info@devnack.com. They can provide guidance and assistance in addressing this vulnerability in your system.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
