{"id":"CVE-2026-98521","title":"drm/i915: fix incorrect RCU teardown order","summary":"In the Linux kernel, the following vulnerability has been resolved:\n\ndrm/i915: fix incorrect RCU teardown order\n\ni915_gem_busy_ioctl uses dma_resv_for_each_fence_unlocked() to iterate\nover the fences in an GEM object without holding a re…","severity":"none","vendor":"Linux","product":"Linux","affected":["Linux >= 912ff2ebd695c582ca4cebf833ad73a378a99f23 < 4d4ca84213327da1f84ef7af3946dea6b14c5d88","Linux >= 912ff2ebd695c582ca4cebf833ad73a378a99f23 < c53db9cc245219af6b528ca022a17ebfa91d80ba","Linux >= 912ff2ebd695c582ca4cebf833ad73a378a99f23 < b12e041aedcf9fa77c6002a49f07eb20d0521b86","Linux >= 912ff2ebd695c582ca4cebf833ad73a378a99f23 < cc890d3f1b15bf6481dc7270fba0b4fbba572813","Linux >= 912ff2ebd695c582ca4cebf833ad73a378a99f23 < 2dd0190e397ec6468095fd3e80e79276a7361449","Linux >= 912ff2ebd695c582ca4cebf833ad73a378a99f23 < d2da6696e0c4e60414706e607029d0bb0330c67e","Linux 5.17"],"published":"2026-10-18","updated":"2026-10-18","sourceUpdated":"2026-10-18T15:17:38.938Z","source":"CVEORG","sourceUrl":"https://www.cve.org/CVERecord?id=CVE-2026-98521","references":[{"url":"https://git.kernel.org/stable/c/4d4ca84213327da1f84ef7af3946dea6b14c5d88"},{"url":"https://git.kernel.org/stable/c/c53db9cc245219af6b528ca022a17ebfa91d80ba"},{"url":"https://git.kernel.org/stable/c/b12e041aedcf9fa77c6002a49f07eb20d0521b86"},{"url":"https://git.kernel.org/stable/c/cc890d3f1b15bf6481dc7270fba0b4fbba572813"},{"url":"https://git.kernel.org/stable/c/2dd0190e397ec6468095fd3e80e79276a7361449"},{"url":"https://git.kernel.org/stable/c/d2da6696e0c4e60414706e607029d0bb0330c67e"}],"tags":["cve.org"],"ingestedAt":"2026-10-18T15:45:12.282Z","slug":"CVE-2026-98521","body":"## Overview\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ndrm/i915: fix incorrect RCU teardown order\n\ni915_gem_busy_ioctl uses dma_resv_for_each_fence_unlocked() to iterate\nover the fences in an GEM object without holding a reference but only\nthe RCU read side lock.\n\nWhat can happen here is that the GEM object is destroyed concurrently\nwhile i915_gem_busy_ioctl is still running. This won't free the GEM\nobjects memory, but still drops all the dma_fence references.\n\nNow when dma_resv_for_each_fence_unlocked() sees a destroyed dma_fence it\nassumes that a new fence list was installed and re-starts the loop.\n\nBut in the case of a destroyed GEM object a new fence list is never\ninstalled, only the old one freed and therefore the iteration never\nfinishes resulting in an endless loop.\n\nThe solution is to drop the fence references only after the RCU grace\nperiod.\n\nThe fixes tag is not necessary the patch introducing the problem, but the\none making it so worse that we need to address it.\n\nThis problem was pointed out by Sashiko-bot.\n\n(cherry picked from commit 5113479556025093bf8133bb2dcaa33be2d50921)\n\n## Affected\n\n- `Linux >= 912ff2ebd695c582ca4cebf833ad73a378a99f23 < 4d4ca84213327da1f84ef7af3946dea6b14c5d88`\n- `Linux >= 912ff2ebd695c582ca4cebf833ad73a378a99f23 < c53db9cc245219af6b528ca022a17ebfa91d80ba`\n- `Linux >= 912ff2ebd695c582ca4cebf833ad73a378a99f23 < b12e041aedcf9fa77c6002a49f07eb20d0521b86`\n- `Linux >= 912ff2ebd695c582ca4cebf833ad73a378a99f23 < cc890d3f1b15bf6481dc7270fba0b4fbba572813`\n- `Linux >= 912ff2ebd695c582ca4cebf833ad73a378a99f23 < 2dd0190e397ec6468095fd3e80e79276a7361449`\n- `Linux >= 912ff2ebd695c582ca4cebf833ad73a378a99f23 < d2da6696e0c4e60414706e607029d0bb0330c67e`\n- `Linux 5.17`\n\n## Remediation\n\nRefer to the linked advisories for vendor-supplied fixes and affected version ranges.","depth":"sunlit","depthScore":3,"depthScoreParts":{"impact":2.8,"likelihood":0,"exploitation":0,"ransomware":0},"changes":[]}