VYPR
Unrated severityNVD Advisory· Published Dec 8, 2025· Updated Apr 15, 2026

CVE-2022-50617

CVE-2022-50617

Description

In the Linux kernel, the following vulnerability has been resolved:

drm/amdgpu/powerplay/psm: Fix memory leak in power state init

Commit 902bc65de0b3 ("drm/amdgpu/powerplay/psm: return an error in power state init") made the power state init function return early in case of failure to get an entry from the powerplay table, but it missed to clean up the allocated memory for the current power state before returning.

AI Insight

LLM-synthesized narrative grounded in this CVE's description and references.

A memory leak in the Linux kernel's AMDGPU powerplay driver occurs when power state initialization fails, leaving allocated memory unfreed.

Vulnerability

Analysis

CVE-2022-50617 describes a memory leak in the Linux kernel's AMDGPU DRM driver, specifically within the powerplay state management (psm) subsystem. The root cause is a missing cleanup in the power state initialization function. When the function fails to retrieve an early return due to a failure to retrieve an entry from the powerplay table, it fails to free the memory that was previously allocated for the current power state. This was introduced by commit 902bc65de0b3, which added the early return but omitted the corresponding kfree() call [1][2].

Exploitation

This vulnerability is triggered during the initialization of the GPU power state, which occurs when the amdgpu driver loads. An attacker would need to have local access to the system and the ability to trigger driver initialization, for example by hotplugging a GPU or reloading the driver module. No special privileges beyond normal user access to trigger the driver are required, but the system must have an AMD GPU using the amdgpu driver. The bug is a memory leak, not a buffer overflow, so exploitation is limited to causing a denial of service by exhausting kernel memory over time.

Impact

An attacker who can repeatedly trigger the driver initialization could cause a gradual depletion of kernel memory, leading to system instability or a denial of service. The leak is small per occurrence, but repeated triggers could exhaust memory. There is no evidence of code execution or privilege escalation from this vulnerability.

Mitigation

The fix was applied in the Linux kernel stable tree with commits 1caed03305b560b and 7cb893264443 [1][2]. Users should update to a kernel version containing these patches. No workaround is available other than avoiding the trigger conditions.

AI Insight generated on May 19, 2026. Synthesized from this CVE's description and the cited reference URLs; citations are validated against the source bundle.

Affected products

1

Patches

4

Vulnerability mechanics

Generated on May 9, 2026. Inputs: CWE entries + fix-commit diffs from this CVE's patches. Citations validated against bundle.

References

4

News mentions

0

No linked articles in our index yet.