Live › vulnerability › CVE-2026-98910
Go to dashboardWhen enabling the AMD KFD debug trap fails while copying runtime info to userspace, the kernel returns an error without undoing the trap setup, leaving a refcount imbalance and inconsistent trap state. The sources do not say that an attacker can gain code execution or read data from this flaw.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 21:57 UTC. All times on this page are UTC.
Systems running a Linux kernel with the amdkfd driver for AMD GPUs, which is used for compute and ROCm workloads. Hosts without AMD GPUs or without the KFD driver loaded are unlikely to be exposed. The sources do not say which kernel versions are affected.
No product ranges from the sources yet.
Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
In the Linux kernel, the following vulnerability has been resolved:
drm/amdkfd: Unwind debug trap enable on copy_to_user failure
If kfd_dbg_trap_enable() fails while copying runtime_info to userspace, it had already activated the trap, set debug_trap_enabled, taken an extra process reference, and opened the debug event file. Return -EFAULT without unwinding that state, leaving inconsistent trap state and a refcount imbalance that could break later DISABLE/ENABLE.
On copy_to_user failure, deactivate the trap and undo the rest of the enable setup before returning.
This page as .md · .json · in your agent: get_signal("CVE-2026-98910")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.