Vulnerability in drm/msm/hdmi Package: Check Return Value after Calling platform_get_resource_byname()
Summary
GSD-2022-1002783: drm/msm/hdmi: check return value after calling platform_get_resource_byname(). Affects Kernel versions >= c6a57a50ad562a2e6fc6ac3218b710caea73a58b, < 9f5495a5c51c1d11c6ffc13aa2befffec0c2651a. 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 identified 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 (such as memory or I/O ports) from the platform device. By not verifying the return value, a malicious actor could exploit this vulnerability to gain unauthorized access or perform other malicious actions. 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 due to a failure to check the return value after calling platform_get_resource_byname(). It is recommended to update the Kernel to version v5.18.3 or later to fix this vulnerability. For further support on vulnerability remediation, please 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 unauthorized access or other security issues.
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 alert you in real-time if the vulnerability is present.
Yes, a fix for this vulnerability is available in Linux Kernel version v5.18.3 or later. It is recommended to update your Kernel to ensure the necessary checks are performed.
There are no known exploits for this vulnerability at this time.
You can find more information about this vulnerability in the GSD-2022-1002783 JSON report available at https://github.com/cloudsecurityalliance/gsd-database/blob/main/2022/1002xxx/GSD-2022-1002783.json
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.