- —Not scoredno CVSS score yet
- 0.21%Exploitation in 30 daysEPSS · top 88% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
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)
Timeline
ID reserved
By Linux
- 23 days later
· 23 days later
Published
- 1 day later
· 1 day later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.
- EPSS (exploitation in 30 days)
- 0.21% · top 88% of all CVEs (11 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.
Affected products
- affected 912ff2ebd695c582ca4cebf833ad73a378a99f23 – < 4d4ca84213327da1f84ef7af3946dea6b14c5d88
- affected 912ff2ebd695c582ca4cebf833ad73a378a99f23 – < c53db9cc245219af6b528ca022a17ebfa91d80ba
- affected 912ff2ebd695c582ca4cebf833ad73a378a99f23 – < b12e041aedcf9fa77c6002a49f07eb20d0521b86
- affected 912ff2ebd695c582ca4cebf833ad73a378a99f23 – < cc890d3f1b15bf6481dc7270fba0b4fbba572813
- affected 912ff2ebd695c582ca4cebf833ad73a378a99f23 – < 2dd0190e397ec6468095fd3e80e79276a7361449
- affected 912ff2ebd695c582ca4cebf833ad73a378a99f23 – < d2da6696e0c4e60414706e607029d0bb0330c67e
- affected 5.17
- unaffected < 5.17
- unaffected 6.1.189 – ≤ 6.1.*
- unaffected 6.6.158 – ≤ 6.6.*
- unaffected 6.12.112 – ≤ 6.12.*
- unaffected 6.18.55 – ≤ 6.18.*
- unaffected 7.2.9 – ≤ 7.2.*
- unaffected 7.3 – ≤ *
References
References6
- https://git.kernel.org/stable/c/4d4ca84213327da1f84ef7af3946dea6b14c5d88 (opens in a new tab)
- https://git.kernel.org/stable/c/c53db9cc245219af6b528ca022a17ebfa91d80ba (opens in a new tab)
- https://git.kernel.org/stable/c/b12e041aedcf9fa77c6002a49f07eb20d0521b86 (opens in a new tab)
- https://git.kernel.org/stable/c/cc890d3f1b15bf6481dc7270fba0b4fbba572813 (opens in a new tab)
- https://git.kernel.org/stable/c/2dd0190e397ec6468095fd3e80e79276a7361449 (opens in a new tab)
- https://git.kernel.org/stable/c/d2da6696e0c4e60414706e607029d0bb0330c67e (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-103761 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-98521)Record last updated .