Description (CNA)
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.
Affected (CNA)
| Vendor / product | Versions |
|---|---|
| Linux / Linux | affected 3e26d9f08fbe0b73e951a5e810fdb7a332b7e37f before 311595dc0b5621f74d8eb4dc38ef4efcdfe7e769; affected 3e26d9f08fbe0b73e951a5e810fdb7a332b7e37f before 06a9460b8b792e109cbc934a856d02e5cff217ef; affected 3e26d9f08fbe0b73e951a5e810fdb7a332b7e37f before 11cef99491117d4264603df159c4ff5f3845a059; affected 3e26d9f08fbe0b73e951a5e810fdb7a332b7e37f before 8662e56c31cf23b61ca3d11b516efb94c35b8026 |
| Linux / Linux | affected 6.11; unaffected 0 before 6.11; unaffected 6.12.110 through 6.12.*; unaffected 6.18.51 through 6.18.*; unaffected 7.2.5 through 7.2.*; unaffected 7.3 through * |
CWE
No CWE identifiers supplied.