# CVE-2026-98270: drm/amdgpu: check ras and obj before dereference

> A null pointer dereference in the AMD GPU driver causes a kernel crash during specific interrupt handling, leading to 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:** 6 Oct 2026
- **Updated:** 19 Oct 2026
- **Also known as:** AZL-106413, BELL-CVE-2026-98270, DEBIAN-CVE-2026-98270, GHSA-q944-85cm-w3r6, UBUNTU-CVE-2026-98270

## What is CVE-2026-98270?

CVE-2026-98270 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: check ras and obj before dereference

nbio_v7_9_handle_ras_controller_intr_no_bifring() dereferences ras and obj
without checking either for NULL. Both amdgpu_ras_get_context() and
amdgpu_ras_find_obj() can return NULL, e.g. during the window between
adev->nbio.ras being set (early in amdgpu_ras_init(), by design, to
enable the fatal-error interrupt as soon as possible) and the PCIE_BIF
ras object actually being created in RAS late_init. Any interrupt in that
window crashes in hard-IRQ context.

This is analogous to commit d190b459b2a4 ("drm/amdgpu: the warning
dereferencing obj for nbio_v7_4"), which fixed the same issue in the
nbio_v7_4 handler.

Found by Linux Verification Center (linuxtesting.org) with SVACE.

(cherry picked from commit c7071767a50a32ed727cf800ac84372429e3b4b3)

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


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

Apply the vendor's patch.

## Is CVE-2026-98270 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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