CVE-2026-98521
Last modified
CVE-2026-98521 is a vulnerability of currently unknown severity. In the Linux kernel, the following vulnerability has been resolved: drm/i915: fix incorrect RCU teardown order i915_gem_busy_ioctl uses dma_resv_for_each_fence_unlocked() to iterate over the fences in an GEM object without holding a reference but only the RCU read side lock. What can happen here is that the GEM object is destroyed concurrently while i915_gem_busy_ioctl is still running. This won't free the GEM objects memory, but still drops all the dma_fence references. Now when dma_resv_for_each_fence_unlocked() sees a destroyed dma_fence it assumes that a new fence list was installed and re-starts the loop. But in the case of a destroyed GEM object a new fence list is never installed, only the old one freed and therefore the iteration never finishes resulting in an endless loop. The solution is to drop the fence references only after the RCU grace period. The fixes tag is not necessary the patch introducing the problem, but the one making it so worse that we need to address it. This problem was pointed out by Sashiko-bot. (cherry picked from commit 5113479556025093bf8133bb2dcaa33be2d50921).
Description
In the Linux kernel, the following vulnerability has been resolved: drm/i915: fix incorrect RCU teardown order i915_gem_busy_ioctl uses dma_resv_for_each_fence_unlocked() to iterate over the fences in an GEM object without holding a reference but only the RCU read side lock. What can happen here is that the GEM object is destroyed concurrently while i915_gem_busy_ioctl is still running. This won't free the GEM objects memory, but still drops all the dma_fence references. Now when dma_resv_for_each_fence_unlocked() sees a destroyed dma_fence it assumes that a new fence list was installed and re-starts the loop. But in the case of a destroyed GEM object a new fence list is never installed, only the old one freed and therefore the iteration never finishes resulting in an endless loop. The solution is to drop the fence references only after the RCU grace period. The fixes tag is not necessary the patch introducing the problem, but the one making it so worse that we need to address it. This problem was pointed out by Sashiko-bot. (cherry picked from commit 5113479556025093bf8133bb2dcaa33be2d50921)
Affected Software
Source: CNA advisory (CVE.org). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | >= 912ff2ebd695c582ca4cebf833ad73a378a99f23, < 4d4ca84213327da1f84ef7af3946dea6b14c5d88; >= 912ff2ebd695c582ca4cebf833ad73a378a99f23, < c53db9cc245219af6b528ca022a17ebfa91d80ba; >= 912ff2ebd695c582ca4cebf833ad73a378a99f23, < b12e041aedcf9fa77c6002a49f07eb20d0521b86; >= 912ff2ebd695c582ca4cebf833ad73a378a99f23, < cc890d3f1b15bf6481dc7270fba0b4fbba572813; >= 912ff2ebd695c582ca4cebf833ad73a378a99f23, < 2dd0190e397ec6468095fd3e80e79276a7361449; >= 912ff2ebd695c582ca4cebf833ad73a378a99f23, < d2da6696e0c4e60414706e607029d0bb0330c67e |
| Linux | Linux | 5.17 |
References
Timeline
- Published
- Last Modified
- Status
- Received
Frequently Asked Questions
What is CVE-2026-98521?
How severe is CVE-2026-98521?
How do I fix CVE-2026-98521?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-98516In the Linux kernel, the following vulnerability has been re…
- CVE-2026-98517In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-98518In the Linux kernel, the following vulnerability has been re…7
- CVE-2026-98519In the Linux kernel, the following vulnerability has been re…
- CVE-2026-9852A CSV injection vulnerability exists in SYS600. Injected mal…7.8
- CVE-2026-98520In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-98522In the Linux kernel, the following vulnerability has been re…
- CVE-2026-98523In the Linux kernel, the following vulnerability has been re…
- CVE-2026-98524In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-98525In the Linux kernel, the following vulnerability has been re…
- CVE-2026-98526In the Linux kernel, the following vulnerability has been re…
- CVE-2026-98527In the Linux kernel, the following vulnerability has been re…
Are you affected by CVE-2026-98521?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
