dma-buf/sync_file: Don't leak fences on merge failure
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ a02b9dc90d844cc7df7b63264e7920cc425052d9 · < ffe000217c5068c5da07ccb1c0f8cce7ad767435| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
dma-buf/sync_file: Don't leak fences on merge failure
Each add_fence() call does a dma_fence_get() on the relevant fence. In the error path, we weren't calling dma_fence_put() so all those fences got leaked. Also, in the krealloc_array failure case, we weren't freeing the fences array. Instead, ensure that i and fences are always zero-initialized and dma_fence_put() all the fences and kfree(fences) on every error path.
From the CVE record · Linux
The Linux kernel's dma-buf/sync_file component leaks fence references when a merge fails and fails to free the fences array if krealloc_array fails. These failure paths can consume resources; the input does not specify how an attacker could trigger them, whether authentication is needed, or whether user interaction is required.
Anyone running the Linux kernel should check whether their version is affected; affected versions are not specified.