iio: buffer: Tie IIO dma fence lock lifetime to the fence
- 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: Tie IIO dma fence lock lifetime to the fence The `iio_dma_fence` implementation currently uses a lock embedded in the `iio_dmabuf_priv`. But the `iio_dma_fence` can outlive the `iio_dmabuf_priv`, which can cause a use-after-free. Tie the lifetime of the lock to the lifetime of the fence by embedding them in the same struct. We can't just hold a reference to the `iio_dmabuf_priv` from the `iio_dma_fence` since `iio_buffer_dmabuf_release()` might sleep and the fence release callback is not allowed to sleep. Note that the `dma_fence` framework now has an internal lock that gets used when the passing `NULL` for `lock` in `dma_fence_init()`, but in order to allow this patch to be backportable use an external lock.
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
From 3e26d9f08fbe0b73e951a5e810fdb7a332b7e37f · fixed in 6865d79fca17a80fbd60c12550ca9a5e0e20e0eb; From 3e26d9f08fbe0b73e951a5e810fdb7a332b7e37f · fixed in 510497e31be4f241103507315a859e2085ccb081; From 3e26d9f08fbe0b73e951a5e810fdb7a332b7e37f · fixed in 8b3e221590181a8beb3735bbabf166df02c839b5; From 3e26d9f08fbe0b73e951a5e810fdb7a332b7e37f · fixed in f25ec4627d935dedfb5fe83bd2c2678cdcc19611
- 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