CVE-2026-80703: Linux Kernel KFD Privilege Escalation Flaw

CVE-2026-80703 Overview

CVE-2026-80703 is a missing authorization vulnerability in the Linux kernel's AMD Kernel Fusion Driver (amdkfd) subsystem. The flaw exists in the KFD_IOC_DBG_TRAP_DISABLE ioctl handler, which failed to verify caller ownership or ptrace authorization before terminating an active GPU debug session. Any local user with access to /dev/kfd could disable another process's debug session without proper permission checks. The maintainers resolved the issue by adding the missing authorization validation, cherry-picked from upstream commit 4db4c5ffd558.

Critical Impact
Local users with /dev/kfd access can terminate GPU debug sessions belonging to other processes, disrupting debugging workflows and potentially interfering with security tooling that relies on GPU debug traps.

Affected Products

Linux kernel builds including the AMD KFD (Kernel Fusion Driver) with GPU debug trap support
Systems exposing the /dev/kfd character device to unprivileged users
Multiple stable branches referenced by kernel.org backport commits 4070909, 99b2fe4, 9e52212, b8c0506, and ce81361

Discovery Timeline

2026-08-28 - CVE-2026-80703 published to NVD
2026-08-30 - Last updated in NVD database

Technical Details for CVE-2026-80703

Vulnerability Analysis

The defect resides in the drm/amdkfd driver, which exposes ioctl operations through /dev/kfd for GPU compute workloads. The KFD_IOC_DBG_TRAP interface allows userspace debuggers to attach to and control GPU debug sessions on target processes. The KFD_IOC_DBG_TRAP_DISABLE subcommand tears down an active debug session on a target process ID.

Before the fix, the disable path skipped the ownership and ptrace capability checks that other debug trap operations enforced. A local process holding a file descriptor on /dev/kfd could invoke the disable operation against an arbitrary target PID and force termination of that target's GPU debug session. This constitutes a missing authorization flaw in a privileged kernel interface.

Root Cause

The root cause is an omitted authorization check in the KFD_IOC_DBG_TRAP_DISABLE handler. The kernel dispatched the operation without validating that the caller owned the target debug session or held PTRACE_MODE_ATTACH on the target task. The upstream fix inserts the same authorization gating that other trap subcommands already performed, ensuring only the debug session owner or a suitably privileged tracer can disable the session.

Attack Vector

Exploitation requires local access and permission to open /dev/kfd. An unprivileged local user issues an ioctl of type KFD_IOC_DBG_TRAP with the KFD_IOC_DBG_TRAP_DISABLE operation against a victim PID that has an active KFD debug session. The kernel terminates the session without verifying the caller's authority. There is no remote attack surface, and no elevated capabilities are required beyond access to the KFD device node.

See the upstream fixes in the kernel.org stable commit ce81361 and related backports for the exact code paths adjusted.

Detection Methods for CVE-2026-80703

Indicators of Compromise

Unexpected termination of GPU debug sessions reported by ROCm debuggers or GPU compute frameworks
Processes opening /dev/kfd that do not belong to known GPU compute or debugger workloads
ioctl calls to /dev/kfd using the KFD_IOC_DBG_TRAP command against PIDs the caller does not own

Detection Strategies

Enable Linux Audit rules on /dev/kfd open and ioctl operations, correlating caller UID with target process ownership
Baseline the set of processes legitimately using AMD KFD debug traps and alert on deviations
Review kernel logs for anomalous KFD debug session teardowns that do not match debugger lifecycle events

Monitoring Recommendations

Ingest audit and kernel telemetry into a centralized analytics pipeline to correlate /dev/kfd access with process ancestry
Alert when non-debugger binaries invoke KFD_IOC_DBG_TRAP ioctls
Track kernel version and patch state across GPU-enabled hosts to confirm remediation coverage

How to Mitigate CVE-2026-80703

Immediate Actions Required

Apply the stable kernel updates containing commits 4070909, 99b2fe4, 9e52212, b8c0506, or ce81361 corresponding to your kernel branch
Inventory hosts exposing /dev/kfd and confirm which users and containers can access the device node
Restrict /dev/kfd access to trusted GPU compute users where the patch cannot be deployed immediately

Patch Information

The fix was cherry-picked from upstream commit 4db4c5ffd5585b72622ecf6ffedf2da258ee23f5. Stable backports are available in the kernel.org repositories: Kernel Git Commit 4070909, Kernel Git Commit 99b2fe4, Kernel Git Commit 9e52212, Kernel Git Commit b8c0506, and Kernel Git Commit ce81361. Rebuild and reboot affected hosts after applying the patch.

Workarounds

Tighten permissions on /dev/kfd so that only members of a trusted GPU compute group can open the device
Remove or restrict the render and video group memberships that grant /dev/kfd access to non-essential accounts
Disable GPU debug trap workflows on multi-tenant systems until the patched kernel is deployed

bash

# Restrict /dev/kfd to a dedicated group and remove world access
sudo groupadd -f kfd-users
sudo chown root:kfd-users /dev/kfd
sudo chmod 660 /dev/kfd

# Verify current kernel version against patched stable releases
uname -r