Refcount Leak in mdp4_modeset_init_intf in drm/msm/mdp4
Summary
GSD-2022-1004631: drm/msm/mdp4: Fix refcount leak in mdp4_modeset_init_intf. Affects Kernel versions >= 86418f90a4c1a0073db65d8a1e2bf94421117a60, < d16a4339825e64f9ddcdff5277982d640bae933b. 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/mdp4 module is responsible for managing the display subsystem on Qualcomm Snapdragon processors. It provides support for the MDP4 (Mobile Display Processor 4) hardware, which is used for rendering and outputting graphics on devices. The mdp4_modeset_init_intf function is a part of this module and is responsible for initializing the display interfaces. However, a refcount leak vulnerability has been identified in this function.
Vulnerability Detail
The refcount leak vulnerability in mdp4_modeset_init_intf can be exploited by an attacker to cause a denial-of-service condition or potentially execute arbitrary code with kernel privileges. The vulnerability occurs due to improper handling of reference counts when initializing display interfaces. By repeatedly triggering the vulnerability, an attacker can exhaust system resources, leading to a system crash or other unexpected behavior. This vulnerability was introduced in Linux Kernel version v4.12 and has been fixed in version v5.10.127.
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 known workaround for this vulnerability. It is recommended to apply the official patch or update the Linux Kernel to the fixed version.
Conclusion
The refcount leak vulnerability in mdp4_modeset_init_intf poses a potential security risk to systems running the affected versions of the Linux Kernel. It is crucial to update the kernel to version v5.10.127 or later to mitigate this vulnerability. For further support and assistance in vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
The vulnerability can lead to a denial-of-service condition or potential execution of arbitrary code with kernel privileges. It may allow an attacker to crash the system or gain unauthorized access to sensitive information.
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 open-source vulnerabilities, including this one.
At the time of this report, there is no known public exploit for this vulnerability. However, it is always recommended to apply security patches promptly to mitigate the risk.
The only effective mitigation for this vulnerability is to update the Linux Kernel to the fixed version. Applying the official patch or upgrading to Linux Kernel v5.10.127 or later will address the refcount leak issue.
This vulnerability was discovered by an automated vulnerability scanning tool and reported to the Linux Kernel security team. The details of the discovery and the fix can be found in the references provided.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
