Use-after-free vulnerability in drm/amdgpu package

Kernel Updated 02 Oct 2025

Summary

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

UVI-2021-1000701: drm/amdgpu: Fix a use-after-free. Affects Kernel versions < 0707c3fea8102d211631ba515ef2159707561b0d. 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 Penetration testing for web, API and mobile 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 GPUs. It is responsible for managing the display and graphics capabilities of AMD graphics cards. The package is widely used in Linux-based systems and is critical for proper functioning of AMD GPUs.

Vulnerability Detail

The use-after-free vulnerability in the drm/amdgpu package allows an attacker to exploit a freed memory region, leading to potential code execution or privilege escalation. This vulnerability occurs when the package fails to properly handle memory deallocation, allowing an attacker to manipulate the freed memory for malicious purposes. If successfully exploited, an attacker could gain unauthorized access to sensitive information or execute arbitrary code with elevated privileges.

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 known workaround for this vulnerability. It is essential to apply the fix by updating the Linux Kernel to the patched version.

Conclusion

The use-after-free vulnerability in the drm/amdgpu package of the Linux Kernel can lead to unauthorized access to sensitive information or arbitrary code execution. It is crucial to update the Linux Kernel to version v4.4.271 or later to mitigate this vulnerability. No known workarounds exist, and it is recommended to apply the fix as soon as possible. For further support, contact DevNack.com.

See every vulnerability recorded for Kernel →

Share this vulnerability

FAQ

If successfully exploited, this vulnerability can lead to unauthorized access to sensitive information or arbitrary code execution with elevated privileges.

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 to the playground, and it will alert you if the vulnerability is present.

There are no known instances of this vulnerability being exploited in the wild. However, it is crucial to apply the fix as soon as possible to mitigate the risk.

Yes, this vulnerability can be exploited remotely if the affected system is accessible over a network. It is recommended to update the Linux Kernel to the patched version to prevent remote exploitation.

For further support on vulnerability remediation, you can contact info@devnack.com. They can provide guidance and assistance in addressing this 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