# CVE-2026-97422: drm/amdkfd: fix SMI event cross-process information leak

> A local user in the render group can monitor all GPU workloads and leak process information due to a missing privilege check in the AMD KFD driver.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 24 Sep 2026
- **Updated:** 21 Oct 2026
- **Also known as:** AZL-103589, BELL-CVE-2026-97422, DEBIAN-CVE-2026-97422, GHSA-p54q-xhjq-3xh7, UBUNTU-CVE-2026-97422

## What is CVE-2026-97422?

CVE-2026-97422 is a vulnerability in Linux, published on 24 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

In the Linux kernel, the following vulnerability has been resolved:

drm/amdkfd: fix SMI event cross-process information leak

kfd_smi_ev_enabled() skips the suser privilege check when pid=0.
PROCESS_START, PROCESS_END, and VMFAULT events are emitted with
pid=0 while carrying another process's PID and command name, so any
/dev/kfd user in the render group can monitor all GPU workloads.

Pass the target process PID into kfd_smi_event_add() for these events
so the existing per-client filter restricts delivery to the owning
process or CAP_SYS_ADMIN subscribers.

## Which versions are affected by CVE-2026-97422?


## How do I fix CVE-2026-97422?

Apply the vendor's patch.

## Is CVE-2026-97422 being exploited?

There is no known exploitation of CVE-2026-97422 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-97422 and fix it if it is affected.

What it is: CVE-2026-97422 is a vulnerability in Linux, published on 24 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-97422 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-97422/ (Markdown: https://insights.sbomify.com/CVE-2026-97422/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-97422
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-97422
- OSV: https://osv.dev/vulnerability/CVE-2026-97422

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-97422/
Summaries are generated and may contain mistakes; the official description above is the record.