iio: buffer: Tie IIO dma fence lock lifetime to the fence (CVE-2026-89940) | HOL Guard CVE

Unknown severity · Source severity not reportedCVE-2026-89940

iio: buffer: Tie IIO dma fence lock lifetime to the fence

Answer in brief

CVE-2026-89940 records a Unknown severity vulnerability in iio: buffer: Tie IIO dma fence lock lifetime to the fence. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Sep 16, 2026Updated Sep 16, 2026Source checked Sep 16, 2026First seen by HOL Sep 16, 2026Material review Sep 16, 2026

Upstream Advisory

Key facts

Risk: Unknown severitySource severity not reported
Exploitation: Not marked as known exploited
Affected software: 2 mapped packages or products
Fix availability: Available

Why this deserves its current priority

A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
Linux/Linuxgeneric	>=3e26d9f08fbe0b73e951a5e810fdb7a332b7e37f <6865d79fca17a80fbd60c12550ca9a5e0e20e0eb \|\| >=3e26d9f08fbe0b73e951a5e810fdb7a332b7e37f <510497e31be4f241103507315a859e2085ccb081 \|\| >=3e26d9f08fbe0b73e951a5e810fdb7a332b7e37f <8b3e221590181a8beb3735bbabf166df02c839b5 \|\| >=3e26d9f08fbe0b73e951a5e810fdb7a332b7e37f <f25ec4627d935dedfb5fe83bd2c2678cdcc19611	6865d79fca17a80fbd60c12550ca9a5e0e20e0eb, 510497e31be4f241103507315a859e2085ccb081, 8b3e221590181a8beb3735bbabf166df02c839b5, f25ec4627d935dedfb5fe83bd2c2678cdcc19611
Linux/Linuxgeneric	6.11	Not reported

Recommended response

Check inventory. Check lockfiles and deployed manifests for Linux/Linux, Linux/Linux.
Review the reported fix. Update Linux/Linux to 6865d79fca17a80fbd60c12550ca9a5e0e20e0eb if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

Published upstream
Sep 16, 2026
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Sep 16, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Sep 16, 2026

Sources and claim methodology

Upstream source 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.

Quoted source text, attributed separately from HOL analysis.