Vulnerability in drm/msm/hdmi package: check return value after calling platform_get_resource_byname()
Summary
GSD-2022-1003626: drm/msm/hdmi: check return value after calling platform_get_resource_byname(). Affects Kernel versions >= c6a57a50ad562a2e6fc6ac3218b710caea73a58b, < d9cb951d11a4ace4de5c50b1178ad211de17079e. 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/hdmi package is a component of the Linux Kernel, which is responsible for managing display and graphics functionality. It provides support for HDMI output on devices using the Qualcomm MSM (Mobile Station Modem) platform. The package interacts with the hardware to configure and control HDMI output. However, a vulnerability has been discovered in the package that could potentially lead to security issues.
Vulnerability Detail
The vulnerability in the drm/msm/hdmi package arises from a failure to check the return value after calling the platform_get_resource_byname() function. This function is used to retrieve a specific resource by its name from the platform. By not verifying the return value, the package may encounter unexpected behavior or even crash, potentially leading to a denial-of-service (DoS) scenario or other security vulnerabilities. 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
In conclusion, the drm/msm/hdmi package in the Linux Kernel is vulnerable to a security issue related to the failure of checking the return value after calling platform_get_resource_byname(). It is recommended to update the Linux Kernel to version v5.10.121 or later to fix this vulnerability. For further support on vulnerability remediation, you can contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
The impact of this vulnerability is not yet proven, but it could potentially lead to a denial-of-service (DoS) scenario or other security vulnerabilities.
You can use Vulert Playground (https://vulert.com/scanner) to check if your system is affected by this vulnerability. Vulert monitors and alerts in real-time for open-source vulnerabilities without requiring access to the code or installation.
The remote exploitability of this vulnerability has not been determined yet. Further analysis is required to assess the potential for remote exploitation.
There are no known instances of this vulnerability being exploited at the moment. However, it is always recommended to apply security patches and updates to mitigate potential risks.
You can find more information about this vulnerability in the GSD-2022-1003626 JSON file available on the GSD Database GitHub repository (https://github.com/cloudsecurityalliance/gsd-database).
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
