iio: buffer: Make IIO DMA fence release RCU-safe
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 6.12.110, 6.18.51, 7.2.5
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
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.
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
From 3e26d9f08fbe0b73e951a5e810fdb7a332b7e37f · fixed in 311595dc0b5621f74d8eb4dc38ef4efcdfe7e769; From 3e26d9f08fbe0b73e951a5e810fdb7a332b7e37f · fixed in 06a9460b8b792e109cbc934a856d02e5cff217ef; From 3e26d9f08fbe0b73e951a5e810fdb7a332b7e37f · fixed in 11cef99491117d4264603df159c4ff5f3845a059; From 3e26d9f08fbe0b73e951a5e810fdb7a332b7e37f · fixed in 8662e56c31cf23b61ca3d11b516efb94c35b8026
- Linux Linux
6.11
- KernelLinux
From 6.11.0 · fixed in 6.12.110; From 6.13.0 · fixed in 6.18.51; From 6.19.0 · fixed in 7.2.5