# CVE-2026-98178: drm/amdgpu: Skip KFD mapping clear before initialization

> A null pointer dereference in the AMD GPU kernel driver can cause a system crash during GPU reset on specific hardware configurations.

- **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:** 6 Oct 2026
- **Updated:** 19 Oct 2026
- **Also known as:** DEBIAN-CVE-2026-98178, GHSA-mcv2-4hx8-7c7c, UBUNTU-CVE-2026-98178

## What is CVE-2026-98178?

CVE-2026-98178 is a vulnerability in Linux, published on 6 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: Skip KFD mapping clear before initialization

amdgpu_amdkfd_clear_kfd_mapping() assumes that a non-NULL kfd_dev
has a fully populated node array. This is not true when KFD device
initialization fails after probe.

For example, kgd2kfd_device_init() sets num_nodes before checking
PCIe atomics support. On Polaris systems without the required atomics,
it returns before allocating nodes[0], but the kfd_dev remains attached
to the amdgpu device. A later GPU reset then dereferences nodes[0]->id.

Require the authoritative KFD initialization flag before walking the
node array, matching the existing KFD reset and teardown paths.

(cherry picked from commit 4ac1835823c47903fbb278bbf474773c46f59edc)

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


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

Apply the vendor's patch.

## Is CVE-2026-98178 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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