CVE-2026-98521: drm/i915: fix incorrect RCU teardown order
drm/i915: fix incorrect RCU teardown order
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.159.1-1 - Upgrade
Upgrade
azurelinux/kernelto a version that resolves this vulnerability.Fixed in 6.6.159.1-1 - 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
linux/Kernelto a version that resolves this vulnerability.Fixed in 6.1.189 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 6.6.158 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 6.12.112 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 6.18.55 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 7.2.9 - Upgrade
Upgrade
Linux kernelto a version that resolves this vulnerability.Patch 5113479556025093bf8133bb2dcaa33be2d50921
Event History
Frequently Asked Questions
What is the practical impact if this race occurs?
The fence iteration in i915_gem_busy_ioctl can restart indefinitely, resulting in an endless loop. This can leave the affected ioctl operation unable to complete.
What concurrent condition is required to trigger the issue?
i915_gem_busy_ioctl must be iterating fences for a GEM object under the RCU read-side lock while that GEM object is destroyed concurrently. Destruction drops the dma_fence references and frees the old fence list without installing a replacement list.
How can I check whether the fix is present in a kernel tree?
Compare the kernel source or vendor patch set with the referenced stable commits: 4d4ca84213327da1f84ef7af3946dea6b14c5d88, c53db9cc245219af6b528ca022a17ebfa91d80ba, and b12e041aedcf9fa77c6002a49f07eb20d0521b86. The fix defers dropping fence references until after the RCU grace period.