Description
In the Linux kernel, the following vulnerability has been resolved:

dmaengine: Fix possible use after free

In dma_release_channel(), check chan->device->privatecnt after call
dma_chan_put(). However, dma_chan_put() call dma_device_put() which could
release the last reference of the device if the DMA provider is already
gone and hence free it.

Fixes it by moving dma_chan_put() after the check.
Published: 2026-08-15
Score: n/a
EPSS: < 1% Very Low
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

The Linux kernel contains a use‑after‑free flaw in the DMA engine subsystem. When dma_release_channel() deallocates a DMA channel, it checks the device reference count after invoking dma_chan_put(), which internally calls dma_device_put(). If the DMA provider has already been removed, dma_device_put() frees the device memory, leaving dma_release_channel() to access memory that has been reclaimed. This can cause a kernel crash or, under the right conditions, allow arbitrary code execution. The weakness is a classic use‑after‑free (CWE‑416) caused by a race condition in reference counting.

Affected Systems

All Linux kernel builds that contain the older DMA engine implementation before the change referenced by the commit series in the provided URLs are affected. The fix was introduced by moving the dma_chan_put() call after the device reference check. Thus, any kernel version that has not yet applied this change—Linux kernels for the Linux vendor—remains vulnerable, though specific version numbers are not listed.

Risk and Exploitability

Because the vulnerability requires the ability to allocate and free DMA channels and to trigger the race condition, it is a local kernel‑level issue that could lead to a system crash or privilege escalation. No CVSS score, EPSS value or KEV listing is provided, so the quantitative risk is uncertain; nevertheless the nature of the flaw warrants high severity when local privilege is available, and the lack of a known exploit suggests the exploitation likelihood is moderate until active exploitation appears.

Generated by OpenCVE AI on August 15, 2026 at 12:18 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Upgrade the Linux kernel to a version that includes the dmaengine use‑after‑free fix
  • If an immediate kernel upgrade is not possible, disable or restrict DMA channel allocation until the fix is applied
  • Apply kernel hardening settings such as CONFIG_STRICT_DEVMEM and enable runtime integrity checks to detect anomalous behavior

Generated by OpenCVE AI on August 15, 2026 at 12:18 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Sat, 15 Aug 2026 12:45:00 +0000

Type Values Removed Values Added
Weaknesses CWE-362
CWE-416

Sat, 15 Aug 2026 06:00:00 +0000

Type Values Removed Values Added
Description In the Linux kernel, the following vulnerability has been resolved: dmaengine: Fix possible use after free In dma_release_channel(), check chan->device->privatecnt after call dma_chan_put(). However, dma_chan_put() call dma_device_put() which could release the last reference of the device if the DMA provider is already gone and hence free it. Fixes it by moving dma_chan_put() after the check.
Title dmaengine: Fix possible use after free
First Time appeared Linux
Linux linux Kernel
CPEs cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
Vendors & Products Linux
Linux linux Kernel
References

Subscriptions

Linux Linux Kernel
cve-icon MITRE

Status: PUBLISHED

Assigner: Linux

Published:

Updated: 2026-08-15T05:57:16.396Z

Reserved: 2026-08-09T03:40:39.934Z

Link: CVE-2026-72476

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Received

Published: 2026-08-15T06:22:21.757

Modified: 2026-08-15T06:22:21.757

Link: CVE-2026-72476

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-08-15T12:30:07Z

Weaknesses
  • CWE-362

    Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')

  • CWE-416

    Use After Free