Vulnerability in drm/amd/display package: Division by Zero
Summary
GSD-2022-1003202: drm/amd/display: Check if modulo is 0 before dividing. Affects Kernel versions < 10ef82d6e0af5536ec64770c07f6bbabfdd6977c. 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/amd/display package is a component of the Linux Kernel, which is responsible for managing display functionality on AMD graphics cards. It provides the necessary drivers and interfaces for rendering graphics and handling display output. This vulnerability specifically affects the display module of the package.
Vulnerability Detail
The vulnerability in the drm/amd/display package arises from a lack of validation before performing a division operation. Specifically, the code fails to check if the modulo is zero before dividing, which can lead to a division by zero error. An attacker could potentially exploit this vulnerability to cause a denial-of-service (DoS) condition or trigger undefined behavior in the system. 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
As a workaround, users can apply the patch provided in commit 10ef82d6e0af5536ec64770c07f6bbabfdd6977c manually to their Linux Kernel installation. The patch adds the necessary validation to check if the modulo is zero before performing the division operation. Here is the code snippet for the patch:
// Add the following code before the division operation
if (modulo == 0) {
// Handle the case when modulo is zero
return;
}
Conclusion
In conclusion, the drm/amd/display package in the Linux Kernel is vulnerable to a division by zero error. This vulnerability can potentially lead to a denial-of-service condition or undefined behavior. It is recommended to update the Linux Kernel to the latest version or apply the provided patch to mitigate the risk. For further support on vulnerability remediation, you can reach out to DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
The impact of this vulnerability can range from a denial-of-service (DoS) condition to undefined behavior in the system. However, the actual impact and attack plausibility have not been proven yet.
To fix this vulnerability, it is recommended to update the Linux Kernel to version v5.15.47 or later. The fix can be found in commit 10ef82d6e0af5536ec64770c07f6bbabfdd6977c of the Linux Kernel repository.
Yes, a workaround is available. Users can manually apply the patch provided in commit 10ef82d6e0af5536ec64770c07f6bbabfdd6977c to their Linux Kernel installation.
The remote exploitability of this vulnerability has not been determined yet. Further analysis is required to assess the potential for remote exploitation.
For more information about this vulnerability, you can refer to the source link: https://github.com/cloudsecurityalliance/gsd-database/blob/main/2022/1003xxx/GSD-2022-1003202.json
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
