CVE-2026-63846: Linux Kernel Privilege Escalation Flaw

CVE-2026-63846 Overview

CVE-2026-63846 is a Linux kernel vulnerability in the AMD GPU (amdgpu) Direct Rendering Manager (DRM) driver. The flaw affects the JPEG v3.0 ring, which does not support 64-bit user fence writes. Prior to the fix, the driver accepted command submissions (CS) that included user fences on JPEG rings. This mismatch between hardware capability and driver behavior creates a local attack surface exploitable by users with GPU access. The upstream fix rejects such submissions by setting the no_user_fence flag for the JPEG v3.0 ring.

Critical Impact
A local, authenticated user with access to the AMD GPU device can submit malformed command streams with user fences on JPEG rings, leading to high impact on confidentiality, integrity, and availability.

Affected Products

Linux kernel branches containing the drm/amdgpu/jpeg driver with JPEG v3.0 ring support
Systems using AMD GPUs that expose the JPEG v3.0 ring through the amdgpu DRM driver
Distributions shipping vulnerable kernel versions prior to the referenced stable commits

Discovery Timeline

2026-07-19 - CVE-2026-63846 published to NVD
2026-07-20 - Last updated in NVD database

Technical Details for CVE-2026-63846

Vulnerability Analysis

The vulnerability resides in the AMD GPU JPEG engine support within the Linux kernel DRM subsystem. JPEG rings in the amdgpu driver process command submissions from userspace clients through the libdrm interface. User fences are 64-bit values written by the GPU to a memory location that userspace polls to detect command completion.

The JPEG v3.0 ring hardware does not support 64-bit user fence writes. Despite this hardware limitation, the driver previously permitted command submissions carrying user fence requests on JPEG rings. The absence of validation allowed malformed or crafted submissions to propagate through the driver, resulting in undefined behavior at the hardware and kernel boundary.

The upstream fix, cherry-picked from commit 4d7d774f100efb5089c86a1fb8c5bf47c63fc9ef, sets the no_user_fence flag on the JPEG v3.0 ring. This causes the CS ioctl path to reject submissions containing user fences before they reach the hardware.

Root Cause

The root cause is missing input validation on the CS submission path for the JPEG v3.0 ring. The driver did not advertise the ring's inability to handle 64-bit user fence writes, so requests were accepted rather than filtered.

Attack Vector

Exploitation requires local access with permissions to open the DRM render node (typically /dev/dri/renderD*). An attacker submits a crafted command buffer via the DRM_IOCTL_AMDGPU_CS ioctl targeting the JPEG ring with a user fence request. Successful exploitation manipulates kernel state associated with GPU scheduling and fence signaling, producing impact on confidentiality, integrity, and availability of the host.

No public proof-of-concept exploit is available at the time of publication, and the flaw is not listed in the CISA Known Exploited Vulnerabilities catalog.

Detection Methods for CVE-2026-63846

Indicators of Compromise

Unexpected kernel warnings or oops messages referencing amdgpu_cs, jpeg_v3_0, or ring fence handling in dmesg
Repeated GPU reset events or JPEG engine hangs logged by the amdgpu driver
Unprivileged processes issuing large volumes of DRM_IOCTL_AMDGPU_CS calls with user fence flags set

Detection Strategies

Audit installed kernel packages against distribution advisories referencing the stable commits 303da82, 48ce007, 5ada37d, a2baf12, and ee035a9
Correlate GPU driver crash telemetry with process identity to surface local users triggering amdgpu faults
Deploy kernel-level tracing (eBPF or ftrace) on the amdgpu_cs_ioctl entry point to log user fence submissions targeting JPEG rings

Monitoring Recommendations

Forward dmesg and journald kernel logs to a central log store and alert on amdgpu fault signatures
Track running kernel versions across the fleet and flag hosts still exposing vulnerable amdgpu builds
Monitor container and VM workloads with GPU passthrough for anomalous GPU ioctl activity from non-graphics processes

How to Mitigate CVE-2026-63846

Immediate Actions Required

Apply the kernel update from your Linux distribution that includes the upstream fix 4d7d774f100efb5089c86a1fb8c5bf47c63fc9ef
Restrict access to /dev/dri/renderD* and /dev/dri/card* to trusted users and service accounts only
Prioritize patching multi-tenant hosts, VDI systems, and workstations where untrusted local users have GPU access

Patch Information

The fix is available in the following upstream stable commits: Kernel Git Commit 303da82, Kernel Git Commit 48ce007, Kernel Git Commit 5ada37d, Kernel Git Commit a2baf12, and Kernel Git Commit ee035a9. The patch sets no_user_fence on the JPEG v3.0 ring so command submissions with user fences are rejected.

Workarounds

Where patching is delayed, remove local user access to the DRM render nodes by tightening group membership on video and render
Disable GPU passthrough for untrusted virtual machines and containers on affected AMD hardware
Unload the amdgpu module on servers that do not require GPU acceleration, using modprobe -r amdgpu after stopping dependent services

bash

# Verify kernel version and confirm the patch is applied
uname -r

# Restrict DRM render node access to trusted users only
sudo chmod 0660 /dev/dri/renderD128
sudo chown root:render /dev/dri/renderD128

# Review users with GPU access
getent group render video