Description
In the Linux kernel, the following vulnerability has been resolved: drm/xe: Make dma-fences compliant with the safe access rules Xe can free some of the data pointed to by the dma-fences it exports. Most notably the timeline name can get freed if userspace closes the associated submit queue. At the same time the fence could have been exported to a third party (for example a sync_fence fd) which will then cause an use- after-free on subsequent access. To make this safe we need to make the driver compliant with the newly documented dma-fence rules. Driver has to ensure a RCU grace period between signalling a fence and freeing any data pointed to by said fence. For the timeline name we simply make the queue be freed via kfree_rcu and for the shared lock associated with multiple queues we add a RCU grace period before freeing the per GT structure holding the lock.
Product status
dd08ebf6c3525a7ea2186e636df064ea47281987 (git) before b17fcce70733c211cb5dabf54f4f9491920b1d92
dd08ebf6c3525a7ea2186e636df064ea47281987 (git) before ba37807d08bae67de6139346a85650cab5f6145a
dd08ebf6c3525a7ea2186e636df064ea47281987 (git) before 683b0e397dad9f26a42dcacf6f7f545a77ce6c06
dd08ebf6c3525a7ea2186e636df064ea47281987 (git) before 6bd90e700b4285e6a7541e00f969cab0d696adde
6.8
Any version before 6.8
6.12.43 (semver)
6.15.11 (semver)
6.16.2 (semver)
6.17 (original_commit_for_fix)
References
git.kernel.org/...c/b17fcce70733c211cb5dabf54f4f9491920b1d92
git.kernel.org/...c/ba37807d08bae67de6139346a85650cab5f6145a
git.kernel.org/...c/683b0e397dad9f26a42dcacf6f7f545a77ce6c06
git.kernel.org/...c/6bd90e700b4285e6a7541e00f969cab0d696adde
