Vulnerability in drm/nouveau package: Off-by-One Error in BIOS Boundary Checking
Summary
GSD-2022-1000112: drm/nouveau: fix off by one in BIOS boundary checking. Affects Kernel versions >= 4d4e9907ff572bb1d1c0f6913ad6e3d6d4525077, < 909d3ec1bf9f0ec534bfc081b77c0836fea7b0e2. 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
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
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 potential of NVIDIA graphics cards. The package is responsible for managing the display, rendering, and other graphics-related functionalities. However, a vulnerability has been identified in the package's BIOS boundary checking mechanism.
Vulnerability Detail
The vulnerability in the drm/nouveau package is an off-by-one error in the BIOS boundary checking. This error allows an attacker to potentially overwrite adjacent memory locations, leading to memory corruption and possible arbitrary code execution. The vulnerability was introduced in version v4.8 of the Linux Kernel and was fixed in version v4.14.265. 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 is vulnerable to an off-by-one error in BIOS boundary checking. This vulnerability can potentially lead to memory corruption and arbitrary code execution. To mitigate the risk, it is recommended to update the Linux Kernel to version v4.14.265 or later. 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 is not yet proven. However, if successfully exploited, it could lead to memory corruption and potential arbitrary code execution.
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, and Vulert will analyze it in real-time to identify any open-source vulnerabilities, including this one.
No specific workaround has been mentioned for this vulnerability. It is recommended to update the Linux Kernel to the fixed version to mitigate the risk.
There are no known exploits for this vulnerability at the moment. However, it is crucial to apply the recommended fix to prevent any potential exploitation.
You can find more information about this vulnerability in the GSD-2022-1000112 JSON report available at https://github.com/cloudsecurityalliance/gsd-database/blob/main/2022/1000xxx/GSD-2022-1000112.json
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
