iio: buffer: Make IIO DMA fence release RCU-safe (CVE-2026-89941) | HOL Guard CVE

Unknown severity · Source severity not reportedCVE-2026-89941

iio: buffer: Make IIO DMA fence release RCU-safe

Answer in brief

CVE-2026-89941 records a Unknown severity vulnerability in iio: buffer: Make IIO DMA fence release RCU-safe. 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 <311595dc0b5621f74d8eb4dc38ef4efcdfe7e769 \|\| >=3e26d9f08fbe0b73e951a5e810fdb7a332b7e37f <06a9460b8b792e109cbc934a856d02e5cff217ef \|\| >=3e26d9f08fbe0b73e951a5e810fdb7a332b7e37f <11cef99491117d4264603df159c4ff5f3845a059 \|\| >=3e26d9f08fbe0b73e951a5e810fdb7a332b7e37f <8662e56c31cf23b61ca3d11b516efb94c35b8026	311595dc0b5621f74d8eb4dc38ef4efcdfe7e769, 06a9460b8b792e109cbc934a856d02e5cff217ef, 11cef99491117d4264603df159c4ff5f3845a059, 8662e56c31cf23b61ca3d11b516efb94c35b8026
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 311595dc0b5621f74d8eb4dc38ef4efcdfe7e769 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: 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.

Quoted source text, attributed separately from HOL analysis.