CVE-2026-98270
drm/amdgpu: check ras and obj before dereference
No known exploitation. EPSS puts it in the 7th percentile. Fixed versions are out.
What to do
Find your product and version, then upgrade to the build on the right.
- LinuxAffected: ≥ 7692e1ee2446fd1940b5caa6e09779504a58881a, < b7c7f07a40037514f8e890aa00f8d7b196d680cfUpgrade to: b7c7f07a40037514f8e890aa00f8d7b196d680cfAffected: ≥ 7692e1ee2446fd1940b5caa6e09779504a58881a, < fc5f845a291fc8175e6857cd6ad042818da192e8Upgrade to: fc5f845a291fc8175e6857cd6ad042818da192e8Affected: ≥ 7692e1ee2446fd1940b5caa6e09779504a58881a, < 37583946d8751f8e285c467d770ac0b609b82a23Upgrade to: 37583946d8751f8e285c467d770ac0b609b82a23Affected: ≥ 7692e1ee2446fd1940b5caa6e09779504a58881a, < 315c22712715491f0dfafdaf2c2b437540e68702Upgrade to: 315c22712715491f0dfafdaf2c2b437540e68702 + 1 more branchStated by: CVE record
Versions as the sources state them. Full version matrix after sign-in
What it is
From the CVE record
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)
In plain language
No plain-language summary for this CVE yet.
Exploitation
Where each signal puts this CVE on the scale from published to confirmed exploited.
- CISA KEV
Not in the catalog. CISA has not confirmed exploitation.
- Public exploits
No public exploit or proof of concept found in the sources we track.
- EPSS
0.2% chance of exploitation activity in the next 30 days, which ranks it in the 7th percentile of scored CVEs.
Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.
Lifecycle
2 events over 0 days, from the signal feeds we watch.
- Publishedrecord updated
Affected products
Sources
References in the record
- git.kernel.org/stable/c/b7c7f07a40037514f8e890aa00f8d7b196d680cf
- git.kernel.org/stable/c/fc5f845a291fc8175e6857cd6ad042818da192e8
- git.kernel.org/stable/c/37583946d8751f8e285c467d770ac0b609b82a23
And 2 more references. See all after sign-in
In the news
Watch the software you run.
My Stack ranks new CVEs for your products by real-world exploitation, so the next serious one reaches you without reading every advisory.
We'll flag the next CVE, public exploit or patch for Linux, not every advisory.
A free account adds
- The full version matrix and every affected product
- Exploit links, proofs of concept and Metasploit modules
- Email alerts for the products you watch
- The same data over REST API, MCP and CLI