Memory Leak Vulnerability in drm/amd/pm Package

Kernel Updated 02 Oct 2025

Summary

28/06/2022
N/A
No i
Unrated
Not published

GSD-2022-1002581: drm/amd/pm: fix a potential gpu_metrics_table memory leak. Affects Kernel versions >= 95868b85764aff2dcbf78d3054076df75446ad15, < 583637d66a70fc7090e12fb0ebbacc33d39e2214. 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/amd/pm package is a component of the Linux Kernel that handles power management for AMD GPUs. It provides functionality for controlling the power state of the GPU and managing performance metrics. The package is critical for proper functioning and optimization of AMD GPUs in Linux systems.

Vulnerability Detail

The identified vulnerability in the drm/amd/pm package is a potential memory leak in the gpu_metrics_table. This memory leak can occur under certain conditions, leading to a gradual consumption of memory resources. If left unaddressed, this vulnerability can result in system instability, performance degradation, and potential denial-of-service attacks. The vulnerability was introduced in version v5.10 of the Linux Kernel and has been fixed in version v5.17.

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

No specific workaround has been provided for this vulnerability. The recommended solution is to apply the kernel update as mentioned in the 'how_to_fix' section.

Conclusion

The memory leak vulnerability in the drm/amd/pm package of the Linux Kernel can lead to system instability and performance degradation. It is crucial to update the Linux Kernel to version v5.17 or later to mitigate this vulnerability. No specific workaround has been provided, and it is recommended to apply the kernel update as soon as possible. For further support on vulnerability remediation, contact DevNack.com.

See every vulnerability recorded for Kernel →

Share this vulnerability

FAQ

The vulnerability can lead to a memory leak in the gpu_metrics_table, potentially causing system instability, performance degradation, and 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 Vulert will provide real-time alerts for open-source vulnerabilities.

The exact attack vector and exploitability of this vulnerability have not been proven. However, if an attacker can trigger the conditions leading to the memory leak, they may be able to exploit it remotely.

There are no known instances of this vulnerability being exploited in the wild. However, it is important to apply the recommended fix to mitigate any potential risks.

For further support and assistance with vulnerability remediation, you can contact info@devnack.com. They can provide guidance and resources to help address 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