CVE-2026-97422: Linux kernel · drm/amdkfd: fix SMI event cross-process information leak
Source GCVE Database
Not known to be exploited · fixed in b8151aeb4f34e913315058c192f78fea2223f36a : update Linux kernel when convenient.
Data as of 30 Oct 2026, 17:53 UTC
Rated Medium by Threat Radar's AI analysis · CVSS not yet scored by NVD
Thin evidence
One scorer or none- Patch
- Available – fixed in b8151aeb4f34e913315058c192f78fea2223f36a, 470319a893f616ef661a63e825a8e1b9b6eddb91, 92a8dba246d371fe268280e5fd74b0955688e6df +2
Exploitation evidence
Disclosed: evidence found.
CVE published 24 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in– |
AI-suggested
The vulnerability has been resolved in the Linux kernel by correcting the privilege check and properly filtering SMI events to restrict delivery to the owning process or CAP_SYS_ADMIN subscribers. Users should apply the official Linux kernel update that includes this fix. No additional mitigation steps are indicated.
Description
A vulnerability in the Linux kernel's drm/amdkfd component allows cross-process information leakage via SMI events. The flaw occurs because the function kfd_smi_ev_enabled() skips a superuser privilege check when the process ID (pid) is zero. This causes PROCESS_START, PROCESS_END, and VMFAULT events to be emitted with pid=0 but containing another process's PID and command name, enabling any user in the render group with access to /dev/kfd to monitor all GPU workloads.
References
- nvd.nist.gov/vuln/detail/CVE-2026-97422 (opens in a new tab)
- git.kernel.org/stable/c/470319a893f616ef661a63e825a8e1b9b6eddb91 (opens in a new tab)
- git.kernel.org/stable/c/5bb2dfa65d8da83e87b2a31c270bc567df69a5ca (opens in a new tab)
- git.kernel.org/stable/c/6fc7ab7fcd7eefb2f371a1d43cf7a860a08f922a (opens in a new tab)
- git.kernel.org/stable/c/92a8dba246d371fe268280e5fd74b0955688e6df (opens in a new tab)
- git.kernel.org/stable/c/b8151aeb4f34e913315058c192f78fea2223f36a (opens in a new tab)