drm/msm: make sure last_fence is always updated
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 86404a9e3013d814a772ac407573be5d3cd4ee0d and Kernel 8ee817ceafba266d9c6f3a09babd2ac7441d9a2b.
In the Linux kernel, the following vulnerability has been resolved: drm/msm: make sure last_fence is always updated Update last_fence in the vm-bind path instead of kernel managed path. last_fence is used to wait for work to finish in vm_bind contexts but not used for kernel managed contexts. This fixes a bug where last_fence is not waited on context close leading to faults as resources are freed while in use. Patchwork: https://patchwork.freedesktop.org/patch/680080/
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | =6.17, >=92395af63a9958615edfa9d4ef1ea72c92a00410 <86404a9e3013d814a772ac407573be5d3cd4ee0d, >=92395af63a9958615edfa9d4ef1ea72c92a00410 <8ee817ceafba266d9c6f3a09babd2ac7441d9a2b | 86404a9e3013d814a772ac407573be5d3cd4ee0d, 8ee817ceafba266d9c6f3a09babd2ac7441d9a2b |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket