dma-buf/dma-resv: check if the new fence is really later
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
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.
From the CVE record · Linux
The Linux kernel's dma-buf/dma-resv code did not check whether a newly added fence was later than existing fences. Local userspace could exploit this condition to force a kernel use-after-free; the input does not specify authentication requirements or any additional user interaction.
Anyone running a Linux kernel that uses dma-buf/dma-resv should check their kernel's status; affected versions are not specified.