---
id: CVE-2026-89940
title: |-
  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`
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_…
severity: high
cvss: 7.8
cvssVector: 'CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H'
vendor: Linux
product: Linux
affected:
  - >-
    Linux >= 3e26d9f08fbe0b73e951a5e810fdb7a332b7e37f <
    6865d79fca17a80fbd60c12550ca9a5e0e20e0eb
  - >-
    Linux >= 3e26d9f08fbe0b73e951a5e810fdb7a332b7e37f <
    510497e31be4f241103507315a859e2085ccb081
  - >-
    Linux >= 3e26d9f08fbe0b73e951a5e810fdb7a332b7e37f <
    8b3e221590181a8beb3735bbabf166df02c839b5
  - >-
    Linux >= 3e26d9f08fbe0b73e951a5e810fdb7a332b7e37f <
    f25ec4627d935dedfb5fe83bd2c2678cdcc19611
  - Linux 6.11
published: '2026-09-16'
updated: '2026-09-16'
sourceUpdated: '2026-09-16T15:18:19.340'
source: NVD
sourceUrl: 'https://nvd.nist.gov/vuln/detail/CVE-2026-89940'
references:
  - url: 'https://git.kernel.org/stable/c/510497e31be4f241103507315a859e2085ccb081'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/6865d79fca17a80fbd60c12550ca9a5e0e20e0eb'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/8b3e221590181a8beb3735bbabf166df02c839b5'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/f25ec4627d935dedfb5fe83bd2c2678cdcc19611'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
tags:
  - nvd
  - cve.org
ingestedAt: '2026-09-16T10:53:53.968Z'
epss: 0.00159
epssPercentile: 0.05435
---

## Overview

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.

## Remediation

Refer to the linked advisories for vendor-supplied fixes and affected version ranges.