drm/xe: Make dma-fences compliant with the safe access rules
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 683b0e397dad9f26a42dcacf6f7f545a77ce6c06, Kernel 6bd90e700b4285e6a7541e00f969cab0d696adde, Kernel b17fcce70733c211cb5dabf54f4f9491920b1d92 and 1 more.
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.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | =6.8, >=dd08ebf6c3525a7ea2186e636df064ea47281987 <683b0e397dad9f26a42dcacf6f7f545a77ce6c06, >=dd08ebf6c3525a7ea2186e636df064ea47281987 <6bd90e700b4285e6a7541e00f969cab0d696adde, >=dd08ebf6c3525a7ea2186e636df064ea47281987 <b17fcce70733c211cb5dabf54f4f9491920b1d92, >=dd08ebf6c3525a7ea2186e636df064ea47281987 <ba37807d08bae67de6139346a85650cab5f6145a | 683b0e397dad9f26a42dcacf6f7f545a77ce6c06, 6bd90e700b4285e6a7541e00f969cab0d696adde, b17fcce70733c211cb5dabf54f4f9491920b1d92, ba37807d08bae67de6139346a85650cab5f6145a |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket