Invalid Parameter Check in msm_dsi_phy_enable
Summary
GSD-2022-1000128: drm/msm/dsi: invalid parameter check in msm_dsi_phy_enable. Affects Kernel versions >= 5c8290284402bf7d2c12269402b3177b899c78b7, < ca63eeb70fcb53c42e1fe54e1735a54d8e7759fd. 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 vulnerability affects the Kernel package in the Linux ecosystem. The Kernel is the core component of an operating system that manages system resources and provides an interface for software to interact with the hardware. The specific vulnerability is found in the drm/msm/dsi module, which is responsible for managing the display subsystem on Qualcomm Snapdragon SoCs. This vulnerability allows for an invalid parameter check in the msm_dsi_phy_enable function, potentially leading to security issues.
Vulnerability Detail
The vulnerability arises from a lack of proper parameter validation in the msm_dsi_phy_enable function of the drm/msm/dsi module. Attackers may exploit this weakness to manipulate parameters and trigger unexpected behavior, potentially leading to security breaches. The impact and attack plausibility of this vulnerability have not been proven yet. The vulnerability was introduced in version v4.3 of the Linux Kernel and has been fixed in version v4.19.228 by commit ca63eeb70fcb53c42e1fe54e1735a54d8e7759fd.
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 vulnerability in the Kernel package's drm/msm/dsi module, specifically in the msm_dsi_phy_enable function, allows for an invalid parameter check. This vulnerability has the potential to be exploited, although its impact and attack plausibility have not been proven. To mitigate the risk, it is recommended to update the Linux Kernel to version v4.19.228 or later. For further support on vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
The impact of this vulnerability is currently unknown as it has not been proven yet. However, if successfully exploited, it could potentially lead to security breaches.
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 and Vulert will analyze it in real-time.
There are no known exploits for this vulnerability at the moment. However, it is always recommended to patch vulnerabilities as soon as possible to mitigate any potential risks.
No, there is no CVE assigned to this vulnerability at the moment.
You can find more information about this vulnerability in the GSD-2022-1000128 entry of the GSD Database maintained by the Cloud Security Alliance. The link to the specific entry is provided in the references section.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
