Skip to main content

Linux Kernel EUVDEUVD-2026-55374

| CVE-2026-68273 HIGH
Race Condition (CWE-362)
2026-08-10 Linux GHSA-vqhc-jp86-9g52
7.8
CVSS 3.1 · Vendor: Linux
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Gain local user account
  2. Delivery
    Access AMD GPU DRM device node
  3. Exploit
    Initiate amdgpu context initialization
  4. Execution
    Race sysfs pstate write against unprotected amdgpu_ctx_init()
  5. Persist
    Trigger use-after-free or NULL dereference in kernel
  6. Impact
    Corrupt kernel heap to escalate privileges or crash system

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A06:2025 - Insecure Design
ASVS 5.0
V15 - Secure Coding and Architecture Concurrency control, locking
MITRE ATT&CK

1 technique across 1 tactic: Privilege Escalation

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Exploitation requires: (1) local authenticated access to the system with a standard (non-root) user account, per CVSS PR:L; (2) an AMD GPU physically present in the system with the amdgpu kernel module loaded and active - systems without AMD GPU hardware or running with amdgpu blacklisted are entirely unaffected; (3) the attacking user must have access to AMD GPU DRM device nodes (typically /dev/dri/renderD* via the 'render' or 'video' group membership on most Linux distributions); (4) the primary use-after-free vector requires timing a context initialization concurrently with a sysfs pstate modification, imposing a practical race window constraint. Remote exploitation is not possible (AV:L). The secondary logic-error defect (incorrect pstate restore at context exit) does not require a race and may be triggerable more deterministically, but its impact is configuration corruption rather than memory unsafety. Systems where local users have no GPU access, or single-user workstations without untrusted local users, have negligible practical risk.

Impact

The CVSS 7.8 score (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H) reflects high-severity local memory corruption with full C/I/A impact, requiring only a standard user account. However, several factors bound real-world risk: EPSS of 0.18% at the 7th percentile indicates the security community does not currently observe widespread exploitation tooling or activity; no CISA KEV listing confirms no confirmed in-the-wild exploitation. The race condition nature of the primary defect introduces practical exploitation difficulty - AC:L in the official vector arguably understates this, as reliable triggering requires timing concurrent sysfs and context operations. The attack surface is further constrained by hardware dependency: only systems with AMD GPUs running the amdgpu kernel module are vulnerable. The net risk profile is: high severity if exploited on applicable hardware, but low current exploitation likelihood. Priority for patching should be elevated on multi-user Linux systems with AMD GPUs (workstations, GPU compute nodes, gaming platforms) where untrusted local users exist.

Exploit ScenarioDerived

A local user with a standard shell account on a Linux workstation or GPU compute node with an AMD GPU races amdgpu_ctx_init() against a concurrent sysfs pstate write to /sys/class/drm/*/device/power_dpm_force_performance_level, triggering a use-after-free or NULL pointer dereference in kernel memory. Successful exploitation could allow the attacker to corrupt kernel heap memory structures, potentially escalating privileges to root, or reliably crashing the kernel (denial of service). No public exploit code has been identified at time of analysis.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
Patch available 0.2% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Aug 14, 2026

Use-after-free and NULL pointer dereference vulnerabilities in the Linux kernel's amdgpu DRM driver allow a local authenticated user to corrupt kernel memory during GPU context initialization. The flaws stem from amdgpu_ctx_init() failing to acquire adev->pm.stable_pstate_ctx_lock, enabling a race between context initialization and concurrent sysfs pstate modifications, alongside a logic error where context finalization incorrectly restores pstate even when ownership has transferred to sysfs. CVSS rates this 7.8 (High), though EPSS at 0.18% (7th percentile) and absence from CISA KEV indicate no confirmed active exploitation at time of analysis.

RemediationAI

Upgrade to a patched kernel version: Linux 6.12.103, 7.1.6, or the 7.2-rc1 development branch, with upstream fixes at https://git.kernel.org/stable/c/23a8726e1d7597fe7c9a59d5dc42ba8b7d345b8a and the three sibling stable commits listed above. Distribution maintainers (Red Hat, Ubuntu, SUSE, Debian) should be monitored for backported stable patches to their supported kernel versions, as kernel.org commits do not always correspond directly to distribution release versions. If immediate patching is infeasible, a targeted compensating control is to restrict local user access to AMD GPU DRM device nodes (e.g., tighten permissions on /dev/dri/renderD* and /dev/dri/card* via udev rules or group membership), which limits which users can trigger amdgpu context operations - note this will prevent GPU compute and rendering workloads for restricted users. As a more aggressive fallback, blacklisting the amdgpu kernel module (echo 'blacklist amdgpu' >> /etc/modprobe.d/blacklist.conf) eliminates the attack surface entirely but disables all AMD GPU functionality including display output on AMD-only systems.

Affected VersionsENISA

Linux 6607901fce79959130db485e7549dacaaeef034e
Linux 6.1
Linux patch: 6.12.103
Linux 79610d3041338dc1ef554d6fd8b3b3e23be527f5 <e06c39cc1c48dca68a5ffd971c23025a52d46634
Linux 79610d3041338dc1ef554d6fd8b3b3e23be527f5 <23a8726e1d7597fe7c9a59d5dc42ba8b7d345b8a
Linux 79610d3041338dc1ef554d6fd8b3b3e23be527f5 <9f9c88eb298c54348be3ca4087f4f4c615065b87
Linux 79610d3041338dc1ef554d6fd8b3b3e23be527f5 <c1dc4ccb82c9e56325d8e7514ca4c90bd1efb351
Linux patch: 7.1.6
Linux 6.0.7 <6.1
Linux patch: 0
Linux patch: 6.18.44
Linux patch: 7.2-rc1

Affected Packages

euvd linux fix: 6.1

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The vulnerability resides in the amdgpu Direct Rendering Manager (DRM) subsystem of the Linux kernel. Two distinct defects are present: first, amdgpu_ctx_init() modifies and reads the adev->pm.stable_pstate_ctx_lock-protected context pointer without acquiring that lock, creating a TOCTOU race exploitable when sysfs simultaneously modifies the stored context pointer, leading to use-after-free or NULL pointer dereference. Second, a logic error causes ctx->stable_pstate (the restore state) to be saved at context creation time rather than at the moment a context actually overrides the pstate; consequently, context finalization restores an incorrect previous state, trampling over any sysfs-set pstate override. The fix redefines ownership semantics: the previous state is saved only when a context actively claims the pstate override, and restoration occurs only if the context is still the current owner. CPE data (cpe:2.3:a:linux:linux:*) confirms broad kernel version scope, with EUVD pinpointing the introducing commit as 79610d3041338dc1ef554d6fd8b3b3e23be527f5. Though CWE is formally unassigned, the description unambiguously describes CWE-416 (Use After Free) and CWE-476 (NULL Pointer Dereference).

Know when the next one hits your stack

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (Linux) PRIMARY 7.8 HIGH
AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
vuln.today AI 7.0 HIGH

Race condition exploitation against a kernel lock requires precise timing (AC:H); PR:L reflects required local user account; full C/I/A impact from kernel memory corruption.

3.1 AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
4.0 AV:L/AC:H/AT:P/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
SUSE 5.5 MEDIUM
AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Red Hat 7.0 MEDIUM

Primary rating from Vendor (Linux).

CVSS VectorVendor: Linux

Attack Vector
Local
Attack Complexity
Low
Privileges Required
Low
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

Lifecycle Timeline

4
CVSS changed
Aug 13, 2026 - 23:37 NVD
7.8 (HIGH)
Patch available
Aug 10, 2026 - 14:18 EUVD
CVE Published
Aug 10, 2026 - 12:01 cve.org
HIGH 7.8
CVE Published
Aug 10, 2026 - 12:01 cve.org
UNKNOWN (no severity yet)

DescriptionCVE.org

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)

Executive ViewAI

Why It Matters

Linux AMD GPU driver vulnerability CVE-2026-68273 creates risk of service outages and kernel security compromise for organizations using GPU acceleration. No public exploit identified at time of analysis (0.2% EPSS), but the CVSS 7.8 rating and requirement for only local authenticated access mean that systems with multiple users or shared GPU resources require immediate patching to prevent potential production impact.

Business Impact: High
Compensating Controls

Apply vendor patch.

Threat Intelligence Overview

EPSS Score
0.2%
Top 93% exploitable
Prevalence
High
Linux kernel powers most cloud, server, and workstation infrastructure globally.
Data Quality
6 sources
Confidence: High

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS 0.2%
Patch available Yes
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation· derived
None
System Exposure· derived
Small
Automatable· derived
No
Human Impact
High

Priority Score

39
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +39
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Race conditions occur when multiple concurrent requests exploit the brief time gap between checking a condition and acting upon it (TOCTOU - Time of Check, Time of Use).

Denial of Service attacks render applications or systems unavailable by overwhelming resources or triggering failure conditions.

Vendor StatusVendor

SUSE

Severity: Moderate
Product Status
SUSE Linux Enterprise Desktop 15 SP7 Affected
SUSE Linux Enterprise Desktop 15 SP7 Affected
SUSE Linux Enterprise High Availability Extension 15 SP7 Affected
SUSE Linux Enterprise High Availability Extension 15 SP7 Affected
SUSE Linux Enterprise High Availability Extension 16.0 Affected

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy