Fix gart.bo pin_count leak in drm/amdgpu

Kernel Updated 02 Oct 2025

Summary

19/10/2021
N/A
No i
Unrated
Not published

GSD-2021-1001576: drm/amdgpu: fix gart.bo pin_count leak. Affects Kernel versions < 83d857d6b0967b6709cd38750c3ce2ed8ced1a95. 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 includes the necessary drivers and functionality to enable graphics acceleration and other GPU-related tasks on AMD hardware. The gart.bo pin_count leak vulnerability affects this package and can potentially lead to security issues.

Vulnerability Detail

The gart.bo pin_count leak vulnerability in drm/amdgpu allows for a pin_count leak in the gart.bo object. This can result in resource leaks and potential memory corruption. An attacker could potentially exploit this vulnerability to gain unauthorized access, execute arbitrary code, or cause a denial of service. The vulnerability has been fixed in Linux Kernel version v5.4.154 by commit 83d857d6b0967b6709cd38750c3ce2ed8ced1a95.

How To Fix

No fixed version is published for this vulnerability.

To fix the gart.bo pin_count leak vulnerability, it is recommended to update the Linux Kernel to version v5.4.154 or later. This can be done by pulling the latest updates from the official Linux Kernel repository using the following command:

$ git pull https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git

After updating the kernel, rebuild and reinstall the updated version to ensure the fix is applied.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Conclusion

The gart.bo pin_count leak vulnerability in drm/amdgpu has been fixed in Linux Kernel version v5.4.154. It is crucial to update the Linux Kernel to the fixed version to ensure the security and stability of the system. For further support on vulnerability remediation, you can reach out to DevNack.com.

See every vulnerability recorded for Kernel →

Share this vulnerability

FAQ

The gart.bo pin_count leak vulnerability can lead to resource leaks and potential memory corruption. It could be exploited by attackers to gain unauthorized access, execute arbitrary code, or cause a denial of service.

Yes, the vulnerability has been fixed in Linux Kernel version v5.4.154 by commit 83d857d6b0967b6709cd38750c3ce2ed8ced1a95.

To fix the vulnerability, update the Linux Kernel to version v5.4.154 or later by pulling the latest updates from the official Linux Kernel repository.

No specific workarounds have been mentioned for this vulnerability. It is recommended to update the Linux Kernel to the fixed version.

For more details about the vulnerability, you can refer to the source link provided in the database specific section of the vulnerability report.

Related vulnerabilities

Recent vulnerabilities recorded for Kernel.

How To Fix

No fixed version is published for this vulnerability.

To fix the gart.bo pin_count leak vulnerability, it is recommended to update the Linux Kernel to version v5.4.154 or later. This can be done by pulling the latest updates from the official Linux Kernel repository using the following command:

$ git pull https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git

After updating the kernel, rebuild and reinstall the updated version to ensure the fix is applied.

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

Follow Vulert in Google

Get more Vulert vulnerability and dependency-security updates in Google Search and AI results.