Vulnerability in drm/nouveau package: Off-by-One Error in BIOS Boundary Checking

Kernel Updated 02 Oct 2025

Summary

18/02/2022
N/A
No i
Unrated
Not published

GSD-2022-1000220: drm/nouveau: fix off by one in BIOS boundary checking. Affects Kernel versions >= 4d4e9907ff572bb1d1c0f6913ad6e3d6d4525077, < f071d9fa857582d7bd77f4906691f73d3edeab73. No fix is published. How to fix ↓

Free scan

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.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

Background

The drm/nouveau package is a component of the Linux Kernel ecosystem. It provides support for NVIDIA GPUs using the Nouveau driver. The package allows users to utilize the full capabilities of their NVIDIA graphics cards on Linux systems. 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 the BIOS boundary checking mechanism. This error allows an attacker to potentially access memory beyond the intended boundaries, leading to various security risks. The impact and attack plausibility of this vulnerability have not been proven yet. The vulnerability was introduced in version v4.8 of the Linux Kernel and has been fixed in version v5.10.99 by commit f071d9fa857582d7bd77f4906691f73d3edeab73.

How To Fix

No fixed version is published for this vulnerability.

To fix this vulnerability, it is recommended to update the Linux Kernel to version v5.10.99 or later. This can be done by pulling the latest updates from the official Linux Kernel repository using the following command:

$ git clone https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/

Once the repository is cloned, navigate to the cloned directory and checkout the latest stable version using the following command:

$ git checkout v5.10.99

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 unauthorized access or code execution. It is crucial to update the Linux Kernel to version v5.10.99 or later to mitigate this vulnerability. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for Kernel →

Share this vulnerability

FAQ

The impact of this vulnerability is not yet proven. However, if successfully exploited, it could potentially lead to unauthorized access to sensitive information or the execution of arbitrary code.

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 the Vulert Playground will analyze it for any open-source vulnerabilities, including this one.

No, there are no known workarounds for this vulnerability. It is recommended to update the Linux Kernel to the fixed version as soon as possible.

The remote exploitability of this vulnerability has not been determined yet. Further analysis is required to assess the potential for remote exploitation.

The vulnerability was discovered by an automated ID intended to aid in the discovery of potential security vulnerabilities. The actual impact and attack plausibility have not been proven yet.

Related vulnerabilities

Recent vulnerabilities recorded for Kernel.

Sponsored Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

How To Fix

No fixed version is published for this vulnerability.

To fix this vulnerability, it is recommended to update the Linux Kernel to version v5.10.99 or later. This can be done by pulling the latest updates from the official Linux Kernel repository using the following command:

$ git clone https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/

Once the repository is cloned, navigate to the cloned directory and checkout the latest stable version using the following command:

$ git checkout v5.10.99

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback

Follow Vulert in Google

Get more Vulert vulnerability and dependency-security updates in Google Search and AI results.