drm/i915: fix incorrect RCU teardown order
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 6.1.189, 6.6.158, 6.12.112, 6.18.55, 7.2.9
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
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
- CVE published
- Record last updated
Affected versions
- Linux Linux
From 912ff2ebd695c582ca4cebf833ad73a378a99f23 · fixed in 4d4ca84213327da1f84ef7af3946dea6b14c5d88; From 912ff2ebd695c582ca4cebf833ad73a378a99f23 · fixed in c53db9cc245219af6b528ca022a17ebfa91d80ba; From 912ff2ebd695c582ca4cebf833ad73a378a99f23 · fixed in b12e041aedcf9fa77c6002a49f07eb20d0521b86; From 912ff2ebd695c582ca4cebf833ad73a378a99f23 · fixed in cc890d3f1b15bf6481dc7270fba0b4fbba572813; From 912ff2ebd695c582ca4cebf833ad73a378a99f23 · fixed in 2dd0190e397ec6468095fd3e80e79276a7361449; From 912ff2ebd695c582ca4cebf833ad73a378a99f23 · fixed in d2da6696e0c4e60414706e607029d0bb0330c67e
- Linux Linux
5.17
- KernelLinux
From 5.17.0 · fixed in 6.1.189; From 6.2.0 · fixed in 6.6.158; From 6.7.0 · fixed in 6.12.112; From 6.13.0 · fixed in 6.18.55; From 6.19.0 · fixed in 7.2.9