Vulnerability in drm/nouveau package: Off-by-One Error in BIOS Boundary Checking
Summary
GSD-2022-1000138: drm/nouveau: fix off by one in BIOS boundary checking. Affects Kernel versions >= 4d4e9907ff572bb1d1c0f6913ad6e3d6d4525077, < b2a21669ee98aafc41c6d42ef15af4dab9e6e882. 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/nouveau package is a component of the Linux Kernel ecosystem. It provides support for NVIDIA GPUs using the Nouveau driver. This driver allows Linux systems to utilize the full capabilities of NVIDIA graphics cards. The package is responsible for managing the display, rendering, and communication with the GPU hardware. However, a vulnerability has been discovered in the package that involves an off-by-one error in BIOS boundary checking.
Vulnerability Detail
The vulnerability in the drm/nouveau package arises from an off-by-one error in BIOS boundary checking. This error allows an attacker to potentially overwrite adjacent memory locations, leading to various security issues. The vulnerability was introduced in version v4.8 of the Linux Kernel and was fixed in version v4.19.228. If left unpatched, an attacker could exploit this vulnerability to execute arbitrary code, escalate privileges, or cause a denial-of-service (DoS) condition. It is important to note that 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 →
Conclusion
In conclusion, the drm/nouveau package in the Linux Kernel was found to have an off-by-one error in BIOS boundary checking. This vulnerability could potentially lead to arbitrary code execution, privilege escalation, or a denial-of-service condition. It is crucial to update the Linux Kernel to version v4.19.228 or later to mitigate this vulnerability. For further support on vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
If exploited, this vulnerability could allow an attacker to execute arbitrary code, escalate privileges, or cause a denial-of-service (DoS) condition.
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 provide real-time monitoring and alerts for open-source vulnerabilities.
No specific workaround has been provided for this vulnerability. It is recommended to update the Linux Kernel to the fixed version.
The details regarding remote exploitation have not been provided. However, it is always advisable to apply security updates promptly to mitigate potential risks.
You can find more information about this vulnerability in the Open Source Vulnerability database maintained by the Cloud Security Alliance. The vulnerability ID is GSD-2022-1000138, and the source can be accessed at https://github.com/cloudsecurityalliance/gsd-database/blob/main/2022/1000xxx/GSD-2022-1000138.json.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
