Vulnerability in drm/edid Package: Connector_bad_edid() Function Allows num_of_ext to Exceed num_blocks
Summary
GSD-2021-1002037: drm/edid: In connector_bad_edid() cap num_of_ext by num_blocks read. Affects Kernel versions >= e11f5bd8228fc3760c221f940b9f6365dbf3e7ed, < a7b45024f66f9ec769e8dbb1a51ae83cd05929c7. 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/edid package is a component of the Linux Kernel, which is responsible for managing display-related functionalities. It includes code for handling Extended Display Identification Data (EDID), which provides information about the capabilities and characteristics of connected display devices. The connector_bad_edid() function within this package is responsible for validating the EDID data received from a display device. However, a vulnerability exists in this function that allows the 'num_of_ext' variable to exceed the 'num_blocks' value read from the EDID data.
Vulnerability Detail
The vulnerability in the connector_bad_edid() function can lead to various security issues. By allowing 'num_of_ext' to exceed 'num_blocks', it may result in buffer overflows or out-of-bounds memory access. An attacker could potentially exploit this vulnerability to execute arbitrary code, escalate privileges, or cause denial-of-service conditions. 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
No specific workaround has been provided for this vulnerability.
Conclusion
The vulnerability in the drm/edid package's connector_bad_edid() function allows the 'num_of_ext' variable to exceed the 'num_blocks' value read from the EDID data. This can potentially lead to security risks such as arbitrary code execution, privilege escalation, or denial-of-service conditions. It is crucial to update the Linux Kernel to version v5.10.75 or later to mitigate this vulnerability. For additional support, please contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
The impact of this vulnerability can vary depending on the attacker's capabilities and intentions. It could potentially lead to arbitrary code execution, privilege escalation, or denial-of-service conditions.
You can use the Vulert Playground (https://vulert.com/scanner) to check if your system is affected by this vulnerability. It analyzes the manifest file (e.g., package-lock.json) of your application and provides real-time alerts for open-source vulnerabilities.
No known exploits for this vulnerability have been reported at the moment. However, it is important to apply the recommended fix to mitigate any potential risks.
The possibility of remote exploitation depends on various factors, including network accessibility and system configuration. It is advisable to update the Linux Kernel to the fixed version to minimize the risk of remote exploitation.
For further support on vulnerability remediation or any related concerns, you can reach out to info@devnack.com. They can provide guidance and assistance in addressing this vulnerability.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
