Vulnerability in drm/amd/amdgpu package: Refcount Leak

Kernel Updated 02 Oct 2025

Summary

04/06/2021
N/A
No i
Unrated
Not published

GSD-2021-1000585: drm/amd/amdgpu: fix refcount leak. Affects Kernel versions < 9fdb8ed37a3a44f9c49372b69f87fd5f61cb3240. 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/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 features such as display output, 3D rendering, and video acceleration. The package is widely used in Linux-based systems that utilize AMD graphics cards. However, a vulnerability has been discovered in this package that could lead to a refcount leak.

Vulnerability Detail

The vulnerability in the drm/amd/amdgpu package is related to a refcount leak. A refcount leak occurs when a reference to a resource is not properly released, resulting in a memory leak. In this case, the refcount leak can be triggered by a specific sequence of operations or inputs, causing the package to allocate memory that is not freed. This can lead to a gradual depletion of system resources and potentially result in a denial-of-service condition. The vulnerability has been assigned the ID GSD-2021-1000585 and was fixed in Linux Kernel version v5.10.42 by commit 9fdb8ed37a3a44f9c49372b69f87fd5f61cb3240.

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 available for this vulnerability. Updating the Linux Kernel to the fixed version is the recommended solution.

Conclusion

The vulnerability in the drm/amd/amdgpu package, which could lead to a refcount leak and gradual depletion of system resources, has been fixed in Linux Kernel version v5.10.42. It is crucial to update the Linux Kernel to the fixed version to ensure the security and stability of systems utilizing the drm/amd/amdgpu package. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for Kernel →

Share this vulnerability

FAQ

The vulnerability can lead to a gradual depletion of system resources and potentially result in a denial-of-service condition.

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

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

The vulnerability itself does not provide remote code execution capabilities. However, if an attacker already has access to the system, they may be able to trigger the refcount leak vulnerability to deplete system resources and potentially disrupt normal operation.

The recommended solution is to update the Linux Kernel to the fixed version. However, if updating the kernel is not feasible in your environment, you can consider implementing additional monitoring and resource management measures to mitigate the impact of the refcount leak vulnerability.

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