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
released, and to handle all transitions under the correct lock.

Instead of at context init time, the previous state is saved only at the
point the context overrides the current state, and is restored on context
exit only if the context is still the owner of the current override state.

(cherry picked from commit 1b5e413713c0a93bc1818394d0ce49aaad21bd27)
Published: 2026-08-10
Score: 7.8 High
EPSS: < 1% Very Low
KEV: No
Impact: Denial of Service via Kernel Crash
Action: Apply Patch
AI Analysis

Impact

The vulnerability resides in the AMDGPU component of the Linux kernel. The driver fails to acquire the pm.stable_pstate_ctx_lock when initializing or destroying GPU contexts. This race condition can trigger a use‑after‑free or a NULL pointer dereference when the driver accesses the pstate context structure, potentially corrupting kernel memory and causing a crash. The bug also allows a context cleanup to restore an incorrect pstate value, further destabilising the system.

Affected Systems

Any system running an unpatched Linux kernel that loads the AMDGPU driver. This includes desktop, laptop, and server machines using the default kernel build and an AMD GPU, as long as the amdgpu module is active and GPU contexts can be created.

Risk and Exploitability

The CVSS base score of 7.8 indicates high severity. The EPSS score of < 1% suggests a low probability of current exploitation. The vulnerability is not in CISA’s KEV catalog. Although the description describes a race condition requiring concurrent access to the driver, it is inferred that the attack can be performed locally by creating or destroying GPU contexts, which typically requires user‑level privileges on the affected system. Successful exploitation would result in a kernel crash, leading to a denial of service, without evidence of privilege escalation or data leakage.

Generated by OpenCVE AI on October 20, 2026 at 13:34 UTC.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade the Linux kernel to a version that includes commit 1b5e4137, which adds proper locking (mitigating CWE‑362) and protects against NULL pointer dereference (mitigating CWE‑476).
  • If a kernel upgrade is not feasible, temporarily unload the amdgpu module or apply a blacklist entry to block GPU context creation, thereby eliminating the race condition and dangling pointer usage.
  • Alternatively, apply any vendor‑supplied backport patch that restores the missing lock and corrects the pointer validation logic, directly addressing the concurrency and null‑dereference weaknesses.

Generated by OpenCVE AI on October 20, 2026 at 13:34 UTC.

Tracking

Sign in to view the affected projects.

Advisories
Source ID Title
Debian DLA Debian DLA DLA-4788-1 linux-6.12 security update
Debian DSA Debian DSA DSA-6466-1 linux security update
Ubuntu USN Ubuntu USN USN-8887-1 Linux kernel vulnerabilities
Ubuntu USN Ubuntu USN USN-8888-1 Linux kernel (Azure) vulnerabilities
Ubuntu USN Ubuntu USN USN-8889-1 Linux kernel (OEM) vulnerabilities
Ubuntu USN Ubuntu USN USN-8887-2 Linux kernel (AWS) vulnerabilities
Ubuntu USN Ubuntu USN USN-8888-2 Linux kernel (Azure) vulnerabilities
Ubuntu USN Ubuntu USN USN-8887-3 Linux kernel vulnerabilities
History

Fri, 30 Oct 2026 12:45:00 +0000


Wed, 21 Oct 2026 13:00:00 +0000


Mon, 19 Oct 2026 21:30:00 +0000

Type Values Removed Values Added
Weaknesses CWE-362

Sat, 17 Oct 2026 13:30:00 +0000

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'total'}, 'version': '2.0.3'}


Thu, 13 Aug 2026 22:45:00 +0000

Type Values Removed Values Added
Metrics cvssV3_1

{'score': 7.0, 'vector': 'CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H'}

cvssV3_1

{'score': 7.8, 'vector': 'CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H'}


Thu, 13 Aug 2026 06:30:00 +0000

Type Values Removed Values Added
Weaknesses CWE-416

Wed, 12 Aug 2026 00:15:00 +0000

Type Values Removed Values Added
References
Metrics threat_severity

None

cvssV3_1

{'score': 7.0, 'vector': 'CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H'}

threat_severity

Moderate


Mon, 10 Aug 2026 20:00:00 +0000

Type Values Removed Values Added
Weaknesses CWE-416
CWE-476

Mon, 10 Aug 2026 12:30:00 +0000

Type Values Removed Values Added
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 released, and to handle all transitions under the correct lock. Instead of at context init time, the previous state is saved only at the point the context overrides the current state, and is restored on context exit only if the context is still the owner of the current override state. (cherry picked from commit 1b5e413713c0a93bc1818394d0ce49aaad21bd27)
Title drm/amdgpu: Fix context pstate override handling
First Time appeared Linux
Linux linux Kernel
CPEs cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
Vendors & Products Linux
Linux linux Kernel
References

Subscriptions

Linux Linux Kernel
cve-icon MITRE

Status: PUBLISHED

Assigner: Linux

Published:

Updated: 2026-10-30T12:28:18.032Z

Reserved: 2026-07-30T09:28:09.379Z

Link: CVE-2026-68273

cve-icon Vulnrichment

Updated: 2026-10-16T15:46:29.580Z

cve-icon NVD

Status : Received

Published: 2026-08-10T13:20:16.343

Modified: 2026-10-30T13:19:42.770

Link: CVE-2026-68273

cve-icon Redhat

Severity : Moderate

Publid Date: 2026-08-10T00:00:00Z

Links: CVE-2026-68273 - Bugzilla

cve-icon OpenCVE Enrichment

Updated: 2026-10-20T13:45:13Z

Weaknesses
  • CWE-362

    Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')

  • CWE-476

    NULL Pointer Dereference