CVE-2026-89941

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.

CVSS

No CVSS.

References

Link	Resource
https://git.kernel.org/stable/c/06a9460b8b792e109cbc934a856d02e5cff217ef
https://git.kernel.org/stable/c/11cef99491117d4264603df159c4ff5f3845a059
https://git.kernel.org/stable/c/311595dc0b5621f74d8eb4dc38ef4efcdfe7e769
https://git.kernel.org/stable/c/8662e56c31cf23b61ca3d11b516efb94c35b8026

Configurations

No configuration.

History

No history.

Information

Published : 2026-09-16 11:17

Updated : 2026-09-16 11:17

NVD link : CVE-2026-89941

Mitre link : CVE-2026-89941

CVE.ORG link : CVE-2026-89941

JSON object : View

Products Affected

No product.

CWE

No CWE.

{"id": "CVE-2026-89941", "cveTags": [], "metrics": {}, "affected": [{"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "affectedData": [{"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git", "vendor": "Linux", "product": "Linux", "versions": [{"status": "affected", "version": "3e26d9f08fbe0b73e951a5e810fdb7a332b7e37f", "lessThan": "311595dc0b5621f74d8eb4dc38ef4efcdfe7e769", "versionType": "git"}, {"status": "affected", "version": "3e26d9f08fbe0b73e951a5e810fdb7a332b7e37f", "lessThan": "06a9460b8b792e109cbc934a856d02e5cff217ef", "versionType": "git"}, {"status": "affected", "version": "3e26d9f08fbe0b73e951a5e810fdb7a332b7e37f", "lessThan": "11cef99491117d4264603df159c4ff5f3845a059", "versionType": "git"}, {"status": "affected", "version": "3e26d9f08fbe0b73e951a5e810fdb7a332b7e37f", "lessThan": "8662e56c31cf23b61ca3d11b516efb94c35b8026", "versionType": "git"}], "programFiles": ["drivers/iio/industrialio-buffer.c"], "defaultStatus": "unaffected"}, {"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git", "vendor": "Linux", "product": "Linux", "versions": [{"status": "affected", "version": "6.11"}, {"status": "unaffected", "version": "0", "lessThan": "6.11", "versionType": "semver"}, {"status": "unaffected", "version": "6.12.110", "versionType": "semver", "lessThanOrEqual": "6.12.*"}, {"status": "unaffected", "version": "6.18.51", "versionType": "semver", "lessThanOrEqual": "6.18.*"}, {"status": "unaffected", "version": "7.2.5", "versionType": "semver", "lessThanOrEqual": "7.2.*"}, {"status": "unaffected", "version": "7.3-rc1", "versionType": "original_commit_for_fix", "lessThanOrEqual": "*"}], "programFiles": ["drivers/iio/industrialio-buffer.c"], "defaultStatus": "affected"}]}], "published": "2026-09-16T11:17:03.733", "references": [{"url": "https://git.kernel.org/stable/c/06a9460b8b792e109cbc934a856d02e5cff217ef", "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"}, {"url": "https://git.kernel.org/stable/c/11cef99491117d4264603df159c4ff5f3845a059", "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"}, {"url": "https://git.kernel.org/stable/c/311595dc0b5621f74d8eb4dc38ef4efcdfe7e769", "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"}, {"url": "https://git.kernel.org/stable/c/8662e56c31cf23b61ca3d11b516efb94c35b8026", "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"}], "vulnStatus": "Received", "descriptions": [{"lang": "en", "value": "In the Linux kernel, the following vulnerability has been resolved:\n\niio: buffer: Make IIO DMA fence release RCU-safe\n\nThe `dma_fence` documentation states that if a custom release\nimplementation is provided, the `dma_fence` object must be freed in an\nRCU-safe way. The current `iio_dma_fence` implementation uses `kfree()`,\nwhich might result in a use-after-free.\n\nRemove the custom `release` implementation. This makes the DMA fence core\nfall back to `dma_fence_free()`, which calls `kfree_rcu()` on the fence.\nThis requires that the fence be the first member of `struct iio_dma_fence`.\n\nUsing the default release method for extended DMA fence structures is a\ncommon pattern."}], "lastModified": "2026-09-16T11:17:03.733", "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"}