CVE-2026-68273

Technical Description

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

drm/amdgpu: Fix context pstate override handling

There are several problems in the context pstate handling code.

The most serious ones are potential use-after-free and NULL pointer

dereferences at context initialization time. Both are due

amdgpu_ctx_init() not holding the adev->pm.stable_pstate_ctx_lock, which

is otherwise used from both sysfs and the context code itself for

modifying and clearing the stored context pointer.

Second issue is that context fini can trample over the pstate

configuration set via sysfs. This is due the restore state

(ctx->stable_pstate) being saved at context init time, and not if, or when

the context actually changes the pstate. As the context exits it will

therefore incorrectly restore to what was set before the sysfs override

was requested.

The simplest fix is to drastically simplify how the state is tracked, by

clearly defining the points at which pstate ownership is taken and

relea

Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

References