CVE-2022-49935
dma-buf/dma-resv: check if the new fence is really later
We use these services and cookies to improve your user experience. You may opt out if you wish, however, this may limit some features on this site.
Please see our statement on Data Privacy.
dma-buf/dma-resv: check if the new fence is really later
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.
Reserved 2025-05-01 | Published 2025-06-18 | Updated 2025-06-18 | Assigner Linuxgit.kernel.org/...c/c4c798fe98adceb642050819cb57cbc8f5c27870
git.kernel.org/...c/a3f7c10a269d5b77dd5822ade822643ced3057f0
Support options
