# CVE-2026-97498: drm/amdgpu/userq: pin mqd and fw object bo to avoid eviction

> Local attackers can trigger system hangs by causing eviction of pinned GPU memory objects in the amdgpu 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:** 28 Sep 2026
- **Also known as:** AZL-103976, BELL-CVE-2026-97498, DEBIAN-CVE-2026-97498, GHSA-v8mw-gxj3-q348, UBUNTU-CVE-2026-97498

## What is CVE-2026-97498?

CVE-2026-97498 is a denial of service 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/amdgpu/userq: pin mqd and fw object bo to avoid eviction

mqd and fw objects are queue core objects which should remain
valid and never be unmapped and evicted for user queues to work
properly.

During eviction if these buffers are evicted the hw continue to
use the invalid addresses and caused page faults and system hung.

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


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

Apply the vendor's patch.

## Is CVE-2026-97498 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-97498 is a denial of service 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-97498 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-97498/ (Markdown: https://insights.sbomify.com/CVE-2026-97498/index.md)
```

## Sources

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

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