# CVE-2026-98784: drm/amdgpu/gfx6: fix firmware leak on teardown

> A resource leak in the AMD GPU kernel driver allows attackers to exhaust system memory, potentially causing a denial of service.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 18 Oct 2026
- **Updated:** 26 Oct 2026
- **Also known as:** AZL-109436, BELL-CVE-2026-98784, DEBIAN-CVE-2026-98784, GHSA-2ff4-rcmq-jgcc, UBUNTU-CVE-2026-98784

## What is CVE-2026-98784?

CVE-2026-98784 is a denial of service vulnerability in Linux, published on 18 Oct 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/gfx6: fix firmware leak on teardown

The firmware requested in gfx_v6_0_init_microcode() is not released
when the GFX block is torn down, leaking the firmware resources.

Add gfx_v6_0_free_microcode() and call it from gfx_v6_0_sw_fini()
to release the PFP, ME, CE and RLC firmware.

(cherry picked from commit 386e81346f95ab0be5a82c5535de932e7a456924)

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


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

Apply the vendor's patch.

## Is CVE-2026-98784 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-98784 is a denial of service vulnerability in Linux, published on 18 Oct 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-98784 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-98784/ (Markdown: https://insights.sbomify.com/CVE-2026-98784/index.md)
```

## Sources

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

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