Cloudanix VulnDB

CVE-2026-63844

High · 7.8

CVSS

7.8

EPSS

0.2%

Published

Jul 19, 2026

CISA due date

—

Cloudanix analysis

Next patch cycle SSVC: Track

A flaw in the Linux kernel's graphics handling for certain AMD chips could let a logged-in user take full control of the computer.

Exploitation
Local Privilege
Attacker needs
Low Privilege
Complexity
Low
Impact
Full Compromise
Component
OS kernel
Class
Improper Input Validation
Remediation
Upgrade
Effort
Medium
Patch risk
Low

What it actually does

The vulnerability permits command stream submissions containing user fences to JPEG v4.0.3 rings that lack support for 64-bit user fence writes, bypassing input validation checks in the amdgpu driver and enabling invalid memory operations.

Why it matters to the business

Local attackers on affected Linux systems with compatible AMD GPUs could achieve full system compromise, leading to data theft, persistence, or ransomware deployment on high-value hosts.

How an attack unfolds

An attacker with local user access crafts a command submission targeting the JPEG ring with user fences; the driver previously failed to reject it, allowing the unsupported 64-bit fence write to trigger undefined behavior that can be chained into privilege escalation or kernel code execution.

How to fix it

Apply the upstream fix that sets no_user_fence and rejects user-fence submissions on JPEG v4.0.3 rings; update to a Linux kernel containing commit 2f6afc97d259d530f4f86c7743efbc573a8da927 or later equivalent distribution patches.

How to confirm the fix worked

Inspect amdgpu/jpeg driver source for the no_user_fence flag on v4.0.3 rings; attempt CS submissions with user fences and confirm they are now rejected with appropriate error returns.

Typical attack path

  1. Gain local shell access on a Linux system with an affected AMD GPU
  2. Locate and target the JPEG v4.0.3 ring via DRM interfaces
  3. Submit a command stream containing user fences
  4. Trigger the invalid fence write to corrupt kernel structures
  5. Escalate to root or kernel-level control

How to detect it

Review kernel logs for amdgpu JPEG ring submission errors or fence-related warnings; inspect audit logs for unusual DRM ioctl activity from non-privileged processes.

What your security team should do

  • Expedite kernel updates on all Linux systems containing AMD GPUs
  • Restrict unprivileged access to GPU device nodes via device permissions or SELinux/AppArmor policies
  • Monitor kernel logs for DRM/amdgpu submission errors until patches are deployed

The record

In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu/jpeg: set no_user_fence for JPEG v4.0.3 ring JPEG rings do not support 64-bit user fence writes, reject CS submissions with user fences. (cherry picked from commit 2f6afc97d259d530f4f86c7743efbc573a8da927)

Affected packages

Ecosystem Package Introduced Fixed

Related vulnerabilities