iio: buffer: Make IIO DMA fence release RCU-safe
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:
iio: buffer: Make IIO DMA fence release RCU-safe
The `dma_fence` documentation states that if a custom release implementation is provided, the `dma_fence` object must be freed in an RCU-safe way. The current `iio_dma_fence` implementation uses `kfree()`, which might result in a use-after-free.
Remove the custom `release` implementation. This makes the DMA fence core fall back to `dma_fence_free()`, which calls `kfree_rcu()` on the fence. This requires that the fence be the first member of `struct iio_dma_fence`.
Using the default release method for extended DMA fence structures is a common pattern.
From the CVE record · Linux
The Linux kernel's IIO DMA fence release implementation uses kfree() where RCU-safe freeing is required, potentially causing a use-after-free when the fence is released. The input does not establish how an attacker could trigger or exploit this condition, or whether access or user interaction is required.
Engineers running Linux kernels with the IIO DMA buffer code should check their affected versions; no version range was provided.