dma-buf/dma-resv: check if the new fence is really later
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel a3f7c10a269d5b77dd5822ade822643ced3057f0 and Kernel c4c798fe98adceb642050819cb57cbc8f5c27870.
In the Linux kernel, the following vulnerability has been resolved: dma-buf/dma-resv: check if the new fence is really later Previously when we added a fence to a dma_resv object we always assumed the the newer than all the existing fences. With Jason's work to add an UAPI to explicit export/import that's not necessary the case any more. So without this check we would allow userspace to force the kernel into an use after free error. Since the change is very small and defensive it's probably a good idea to backport this to stable kernels as well just in case others are using the dma_resv object in the same way.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | =5.0, >=27836b641c1bf693c96c627388497b4e0f57441b <a3f7c10a269d5b77dd5822ade822643ced3057f0, >=27836b641c1bf693c96c627388497b4e0f57441b <c4c798fe98adceb642050819cb57cbc8f5c27870 | a3f7c10a269d5b77dd5822ade822643ced3057f0, c4c798fe98adceb642050819cb57cbc8f5c27870 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket