Off-by-one vulnerability in drm/dp package
Summary
GSD-2022-1001777: drm/dp: Fix off-by-one in register cache size. Affects Kernel versions >= e2e16da398d9149ede0162a55f44537582aed2e7, < e912d697400c5f4bc8c1c8090416dad6c59cb28c. 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/dp package is a component of the Linux Kernel that handles display-related functionality for systems using DisplayPort (DP) technology. It provides the necessary drivers and interfaces for managing DP connections and rendering graphics on DP displays. The package is an integral part of the Linux Kernel and is widely used across various Linux distributions.
Vulnerability Detail
The vulnerability in the drm/dp package is an off-by-one error in the register cache size. This error was introduced in version v5.12 of the Linux Kernel by commit e2e16da398d9149ede0162a55f44537582aed2e7 and affects all subsequent versions until it was fixed in v5.15.33 by commit e912d697400c5f4bc8c1c8090416dad6c59cb28c. The off-by-one error can potentially lead to memory corruption or other security issues when handling register cache operations. However, 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 available for this vulnerability. The recommended solution is to update the Linux Kernel to the fixed version.
Conclusion
The off-by-one vulnerability in the drm/dp package of the Linux Kernel can potentially lead to memory corruption or other security issues. It is recommended to update the Linux Kernel to version v5.15.33 or later to fix this vulnerability. If you have any further questions or need assistance with vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
The impact of this vulnerability is currently unknown as no specific attack scenarios have been proven. However, it has the potential to lead to memory corruption or other security issues.
You can use the Vulert Playground (https://vulert.com/scanner) to check if your system is affected by this vulnerability. Simply upload your package-lock.json file and the Vulert Playground will analyze it for any open-source vulnerabilities, including this one.
Yes, a patch for this vulnerability is available in the Linux Kernel version v5.15.33. It is recommended to update to this version or a later one to fix the vulnerability.
Unfortunately, there are no specific temporary measures or workarounds available for this vulnerability. The best course of action is to update the Linux Kernel as soon as possible.
You can find more information about this vulnerability in the GSD-2022-1001777 entry of the GSD database maintained by the Cloud Security Alliance. The entry provides additional details and references to the relevant commits in the Linux Kernel repository.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
