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

Kernel Updated 02 Oct 2025

Summary

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

GSD-2022-1000657: drm/nouveau: fix off by one in BIOS boundary checking. Affects Kernel versions >= 4d4e9907ff572bb1d1c0f6913ad6e3d6d4525077, < e7c36fa8a1e63b08312162179c78a0c7795ea369. 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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The drm/nouveau package is a part of the Linux Kernel ecosystem and is responsible for providing support for NVIDIA GPUs. It includes the Nouveau driver, which is an open-source driver for NVIDIA graphics cards. The package enables users to utilize the full capabilities of their NVIDIA GPUs 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 vulnerability was introduced in version v4.8 of the Linux Kernel and was fixed in version v5.16.8. If left unpatched, an attacker could exploit this vulnerability to execute arbitrary code, escalate privileges, or cause a denial-of-service (DoS) condition.

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 manually to their existing kernel version. Here is an example of how to apply the patch:

  1. Download the patch file from the Linux Kernel repository.
  2. Navigate to the kernel source code directory.
  3. Apply the patch using the 'patch' command: patch -p1 < patch_file.patch
  4. Recompile and install the kernel.

Note: It is recommended to consult the official documentation or seek assistance from the Linux Kernel community for detailed instructions on applying patches.

Conclusion

In conclusion, the drm/nouveau package in the Linux Kernel was found to have an off-by-one error in the BIOS boundary checking mechanism. This vulnerability could allow an attacker to execute arbitrary code, escalate privileges, or cause a denial-of-service (DoS) condition. It is crucial to update the kernel to version v5.16.8 or later to fix this vulnerability. Users can also apply the provided patch as a temporary workaround. For further support and assistance in vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for Kernel →

Share this vulnerability

FAQ

If exploited, this vulnerability can allow an attacker to execute arbitrary code, escalate privileges, or cause a denial-of-service (DoS) condition.

You can use tools like Vulert to check if your system is affected by this vulnerability. Vulert analyzes the package-lock.json file and provides real-time alerts for open-source vulnerabilities.

At the time of this report, there is no known public exploit for this vulnerability. However, it is crucial to apply the necessary updates and patches to mitigate the risk.

Yes, this vulnerability can be exploited remotely if the affected system is accessible over the network. It is recommended to update the kernel as soon as possible to prevent potential attacks.

If you cannot immediately update the kernel, you can apply the provided patch manually to mitigate the vulnerability. However, it is highly recommended to update the kernel as soon as possible to ensure the latest security fixes are in place.

Related vulnerabilities

Recent vulnerabilities recorded for Kernel.

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 →

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