Fix Potential Memory Leak in drm/amd/amdgpu Package

Kernel Updated 02 Oct 2025

Summary

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

GSD-2021-1002552: drm/amd/amdgpu: fix potential memleak. Affects Kernel versions < 75752ada77e0726327adf68018b9f50ae091baeb. 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 drm/amd/amdgpu package is a component of the Linux Kernel that provides support for AMD GPUs. It is responsible for managing the graphics hardware and enabling communication between the GPU and the operating system. This package is widely used in Linux distributions and is critical for proper functioning of AMD GPUs on Linux systems.

Vulnerability Detail

The identified vulnerability in the drm/amd/amdgpu package is a potential memory leak. This means that under certain conditions, the package may fail to release allocated memory, leading to a gradual accumulation of memory over time. If left unaddressed, this could result in excessive memory consumption, potentially causing system instability, performance degradation, or even denial of service.

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

There is no specific workaround mentioned for this vulnerability. The recommended approach is to apply the fix by updating the Linux Kernel.

Conclusion

The potential memory leak in the drm/amd/amdgpu package can be mitigated by updating the Linux Kernel to version v5.15.7 or later. This update includes a fix for the vulnerability, preventing excessive memory consumption and potential system instability. For further support on vulnerability remediation, you can reach out to DevNack.com.

See every vulnerability recorded for Kernel →

Share this vulnerability

FAQ

The potential memory leak in the drm/amd/amdgpu package can lead to excessive memory consumption, which may cause system instability, performance degradation, or denial of service.

You can use tools like Vulert Playground (https://vulert.com/scanner) to check if your system is affected by this vulnerability. Vulert Playground allows you to analyze your manifest file (e.g., package-lock.json) and provides real-time alerts for open-source vulnerabilities.

At the time of this report, there is no known exploit for this vulnerability. However, it is important to apply the fix promptly to prevent any potential exploitation.

The vulnerability is present in versions of the Linux Kernel prior to v5.15.7. Therefore, systems running older versions may be affected, and it is recommended to update to the latest stable version.

For more details about this vulnerability, you can refer to the source link provided in the database_specific section of this report.

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