CVE Catalog

CVE-2026-89941

HighCVSS 7.8
Published: Updated: Translated: NVD NIST

Summary

In the Linux kernel, in the IIO buffer subsystem, the iio_dma_fence implementation uses kfree() to free the dma_fence object, which violates the dma_fence documentation requiring RCU-safe freeing. This might result in a use-after-free.

Risk Assessment

Use-after-free can lead to memory corruption, system crashes, or potential arbitrary code execution in kernel context.

Recommendation

Update the Linux kernel to a version containing the fix that removes the custom release implementation and lets the DMA fence core fall back to dma_fence_free(), which calls kfree_rcu().

Other vulnerabilities in Linux kernel

See all
Original NVD description (English source)

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.

Vulnerability data from NVD (NIST) · CISA KEV · EPSS