Out-of-Bound Writes in drm/amdgpu Package

Kernel Updated 02 Oct 2025

Summary

14/11/2021
N/A
No i
Unrated
Not published

GSD-2021-1002128: drm/amdgpu: Fix even more out of bound writes from debugfs. Affects Kernel versions >= 918698d5c2b50433714d2042f55b55b090faa167, < 9eb4bdd554fc31a5ef6bf645a20ff21618ce45a9. 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 enables graphics rendering and display functionality for AMD graphics cards. The package interacts with the hardware through the debugfs interface, which allows users to access and modify internal GPU parameters for debugging purposes.

Vulnerability Detail

The vulnerability in the drm/amdgpu package involves out-of-bound writes from the debugfs interface. This can occur when certain parameters passed through debugfs are not properly validated, leading to memory corruption and potential privilege escalation attacks. An attacker with local access to the system could exploit this vulnerability to gain elevated privileges or crash the system. The vulnerability was introduced in Linux Kernel version v5.10 and has been fixed in version v5.14.16.

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

As a temporary workaround, users can disable the debugfs interface by removing the debugfs mount point or restricting access to it. This can be done by modifying the system's fstab file or using the mount command with appropriate options. However, disabling debugfs may impact the ability to debug and monitor GPU performance.

Conclusion

The vulnerability in the drm/amdgpu package can lead to out-of-bound writes and potential privilege escalation attacks. It is crucial to update the Linux Kernel to version v5.14.16 or later to fix this vulnerability. Alternatively, users can disable the debugfs interface as a temporary workaround. For further assistance and support in vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for Kernel →

Share this vulnerability

FAQ

The vulnerability can potentially allow an attacker to gain elevated privileges or crash the system by exploiting out-of-bound writes in the drm/amdgpu package.

Any system running Linux Kernel version v5.10 to v5.14.15 with the drm/amdgpu package is affected by this vulnerability.

At the time of this report, there are no known public exploits targeting this vulnerability. However, it is advisable to apply the recommended fixes as soon as possible to mitigate any potential risks.

No, this vulnerability requires local access to the system to exploit it.

Updating the kernel is the recommended solution to fix this vulnerability. However, as a temporary workaround, users can disable the debugfs interface 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