Use-after-free vulnerability in drm/amdgpu package

Kernel Updated 02 Oct 2025

Summary

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

GSD-2021-1000650: drm/amdgpu: Fix a use-after-free. Affects Kernel versions < a849e218556f932576c0fb1c5a88714b61709a17. 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/amdgpu package is a component of the Linux Kernel that provides support for AMD Radeon GPUs. It is responsible for managing the graphics hardware and enabling display functionality. The package is widely used in Linux-based systems that utilize AMD graphics cards. However, a use-after-free vulnerability has been discovered in the package, which can lead to potential security risks.

Vulnerability Detail

The use-after-free vulnerability in the drm/amdgpu package occurs when a memory location is accessed after it has been freed. This can result in the execution of arbitrary code or a system crash. Attackers may exploit this vulnerability to gain unauthorized access, escalate privileges, or cause denial-of-service attacks. The vulnerability was introduced in an unknown version and has been fixed in Linux Kernel version v4.19.193 by commit a849e218556f932576c0fb1c5a88714b61709a17.

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. However, users can mitigate the risk by keeping their systems up to date with the latest kernel updates and following best practices for system security.

Conclusion

The use-after-free vulnerability in the drm/amdgpu package can pose significant security risks to systems utilizing AMD Radeon GPUs. It is crucial to update the Linux Kernel to version v4.19.193 or later to fix this vulnerability. Regularly updating the kernel and following best practices for system security is essential to ensure the protection of your system. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for Kernel →

Share this vulnerability

FAQ

The use-after-free vulnerability in the drm/amdgpu package can potentially allow attackers to execute arbitrary code, gain unauthorized access, escalate privileges, or cause denial-of-service attacks.

You can use the Vulert Playground at Vulert Scanner to check if your system is affected by this vulnerability. Simply upload your package-lock.json file and it will provide real-time alerts for open-source vulnerabilities.

Yes, the vulnerability has been fixed in Linux Kernel version v4.19.193 by commit a849e218556f932576c0fb1c5a88714b61709a17. It is recommended to update the kernel to this version or later.

Yes, this vulnerability can be exploited remotely if an attacker can gain access to the affected system.

There are no known instances of this vulnerability being exploited in the wild. However, it is important to apply the necessary updates to mitigate the risk.

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