Memory Leak in drm/nouveau/debugfs in Linux Kernel

Kernel Updated 02 Oct 2025

Summary

19/10/2021
N/A
No i
Unrated
Not published

GSD-2021-1001504: drm/nouveau/debugfs: fix file release memory leak. Affects Kernel versions >= 6e9fc177399f08446293fec7607913fdbc95e191, < df0c9418923679bc6d0060bdb1b5bf2c755159e0. 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 Devnack Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The Linux Kernel is the core component of the Linux operating system, responsible for managing system resources and providing an interface for communication between hardware and software. The drm/nouveau/debugfs module is a part of the kernel's Direct Rendering Manager (DRM) subsystem, specifically designed for the Nouveau graphics driver. The debugfs filesystem provides a mechanism for exposing debugging and diagnostic information to userspace. However, a vulnerability has been identified in the drm/nouveau/debugfs module that can lead to a memory leak.

Vulnerability Detail

The vulnerability in drm/nouveau/debugfs is caused by a memory leak that occurs when a file is released. This can result in the consumption of excessive memory resources over time, leading to performance degradation or even system instability. An attacker may be able to exploit this vulnerability to exhaust system memory, causing a denial-of-service condition. The vulnerability was introduced in version v4.5 of the Linux Kernel and has been fixed in version v4.9.287.

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 temporary workaround, users can disable the debugfs filesystem by adding the following line to the kernel command line during boot: 'debugfs=none'. This will prevent the vulnerable functionality from being accessible, but it may also disable other legitimate uses of the debugfs filesystem. Therefore, it is recommended to apply the official fix as soon as possible.

Conclusion

In conclusion, a memory leak vulnerability has been discovered in the drm/nouveau/debugfs module of the Linux Kernel. This vulnerability can lead to performance degradation, system instability, and potential denial-of-service attacks. It is recommended to update the Linux Kernel to version v4.9.287 or later to fix this vulnerability. Alternatively, users can apply a temporary workaround by disabling the debugfs filesystem. For further support and assistance in vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for Kernel →

Share this vulnerability

FAQ

This vulnerability can lead to a memory leak, potentially causing performance degradation or system instability. It may also be possible for an attacker to exploit this vulnerability to launch a denial-of-service attack by exhausting system memory.

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

Yes, a patch for this vulnerability is available in version v4.9.287 of the Linux Kernel. It is recommended to update to this version or a later one to fix the vulnerability.

Yes, as a temporary workaround, you can disable the debugfs filesystem by adding 'debugfs=none' to the kernel command line during boot. However, it is recommended to apply the official fix as soon as possible.

You can find more information about this vulnerability in the vulnerability database maintained by the Cloud Security Alliance. The specific vulnerability ID is GSD-2021-1001504.

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