CVE-2026-98270: drm/amdgpu: check ras and obj before dereference
drm/amdgpu: check ras and obj before dereference
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 6.6.158.1-1 - Upgrade
Upgrade
debian/linuxto a version that resolves this vulnerability.Fixed in 6.1.176-1Fixed in 6.1.190-1Fixed in 6.12.115-2Fixed in 7.2.12-1Fixed in 7.2.15-1 - Upgrade
Upgrade
debian/linux-6.12to a version that resolves this vulnerability.Fixed in 6.12.113-1~deb12u1 - Upgrade
Upgrade
ubuntu/linux-hwe-7.0to a version that resolves this vulnerability.Fixed in 7.0.0-42.42~24.04.1 - Upgrade
Upgrade
ubuntu/linux-riscv-7.0to a version that resolves this vulnerability.Fixed in 7.0.0-42.42.1~24.04.1 - Upgrade
Upgrade
ubuntu/linuxto a version that resolves this vulnerability.Fixed in 7.0.0-42.42 - Upgrade
Upgrade
ubuntu/linux-awsto a version that resolves this vulnerability.Fixed in 7.0.0-1016.17 - Upgrade
Upgrade
ubuntu/linux-gcpto a version that resolves this vulnerability.Fixed in 7.0.0-1016.18 - Upgrade
Upgrade
ubuntu/linux-ibmto a version that resolves this vulnerability.Fixed in 7.0.0-1017.17 - Upgrade
Upgrade
ubuntu/linux-oem-7.0to a version that resolves this vulnerability.Fixed in 7.0.0-1017.17 - Upgrade
Upgrade
ubuntu/linux-oracleto a version that resolves this vulnerability.Fixed in 7.0.0-1015.16 - Upgrade
Upgrade
ubuntu/linux-riscvto a version that resolves this vulnerability.Fixed in 7.0.0-42.42.1 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Patch c7071767a50a32ed727cf800ac84372429e3b4b3
Event History
Frequently Asked Questions
When can this crash occur?
The crash can occur if a relevant interrupt arrives after adev->nbio.ras is set during early RAS initialization but before the PCIE_BIF RAS object is created during RAS late initialization. The NULL dereference occurs in hard-IRQ context.
What conditions are required to trigger the issue?
An attacker or triggering condition would need to cause the affected NBIO RAS controller interrupt during the initialization window where the RAS context or PCIE_BIF RAS object has not yet been created. The description does not establish a remote or unprivileged exploitation path.
What is the immediate mitigation if an updated kernel cannot be deployed?
The provided information identifies the vulnerable period as RAS initialization and requires an interrupt during that window, but it does not document a supported configuration workaround. Prioritize applying a kernel build containing the NULL checks in the affected handler.