Potential Deadlock in GPU Reset in drm/amd/amdgpu

Kernel Updated 02 Oct 2025

Summary

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

GSD-2021-1000620: drm/amd/amdgpu: fix a potential deadlock in gpu reset. Affects Kernel versions < de2bf5de17be2b552d18ddea9a16b233f4f009e3. 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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

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-based systems that utilize AMD graphics cards. However, a potential deadlock vulnerability has been identified in the GPU reset functionality of the package.

Vulnerability Detail

The vulnerability in drm/amd/amdgpu arises from a potential deadlock situation during GPU reset. A deadlock occurs when two or more processes are unable to proceed because each is waiting for the other to release a resource. In this case, the deadlock can occur when a GPU reset is triggered while other processes are accessing the GPU. This can lead to a system freeze or crash, impacting the stability and availability of the affected system. The vulnerability has been addressed in Linux Kernel version v5.4.124 by commit de2bf5de17be2b552d18ddea9a16b233f4f009e3.

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.

Conclusion

The potential deadlock vulnerability in drm/amd/amdgpu can lead to system freezes or crashes, impacting the stability and availability of affected systems. It is crucial to update the Linux Kernel to version v5.4.124 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 vulnerability can lead to a system freeze or crash, affecting the stability and availability of the affected system.

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 potential vulnerabilities.

At the time of this report, there is no known exploit for this vulnerability. However, it is important to apply the recommended fix to ensure the security and stability of your system.

No, this vulnerability requires local access to the affected system in order to trigger the GPU reset and potentially cause a deadlock.

The recommended solution is to update the Linux Kernel to the fixed version. However, if updating the Kernel is not feasible, you can consider disabling GPU reset functionality if it is not essential for your system's operation. This can be done by modifying the Kernel configuration or using kernel boot parameters.

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