iio: buffer: Make IIO DMA fence release RCU-safe
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 8662e56c31cf23b61ca3d11b516efb94c35b8026, Kernel 06a9460b8b792e109cbc934a856d02e5cff217ef, Kernel 11cef99491117d4264603df159c4ff5f3845a059 and 4 more.
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
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | >=3e26d9f08fbe0b73e951a5e810fdb7a332b7e37f <8662e56c31cf23b61ca3d11b516efb94c35b8026, >=3e26d9f08fbe0b73e951a5e810fdb7a332b7e37f <06a9460b8b792e109cbc934a856d02e5cff217ef, >=3e26d9f08fbe0b73e951a5e810fdb7a332b7e37f <11cef99491117d4264603df159c4ff5f3845a059, >=3e26d9f08fbe0b73e951a5e810fdb7a332b7e37f <311595dc0b5621f74d8eb4dc38ef4efcdfe7e769, =6.11 | 8662e56c31cf23b61ca3d11b516efb94c35b8026, 06a9460b8b792e109cbc934a856d02e5cff217ef, 11cef99491117d4264603df159c4ff5f3845a059, 311595dc0b5621f74d8eb4dc38ef4efcdfe7e769 |
| linux-kernel: Kernel | >=6.13.0 <6.18.51, >=6.19.0 <7.2.5, >=6.11.0 <6.12.110 | 6.18.51, 7.2.5, 6.12.110 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket