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

dmaengine: dw-edma: Serialize channel state checks

pause() and resume() read and update channel state without holding vc.lock,
while the interrupt handlers update the same state under it. Take the same
lock around those state checks so that request, status, and configured stay
consistent.

For example, pause() can observe EDMA_ST_BUSY right before the interrupt
handler completes the final descriptor and moves the channel to
EDMA_ST_IDLE, and then record EDMA_REQ_PAUSE on an already idle channel. No
further interrupt will acknowledge the request, and since issue_pending()
requires EDMA_REQ_NONE, the channel is wedged for good: terminate_all()
leaves the stale request behind, so even reconfiguring the channel does not
recover it.

issue_pending() already runs under vc.lock, but it tests configured before
taking it. Move that test under the lock as well, so configured, request,
and status are evaluated as one channel-state snapshot.
Published: 2026-09-17
Score: n/a
EPSS: < 1% Very Low
KEV: No
Impact: Denial of Service – DMA channel can become permanently wedged
Action: Immediate patch
AI Analysis

Impact

The dw‑edma driver in the Linux kernel contains a race condition where pause() and resume() modify channel state without acquiring vc.lock while the interrupt handler updates the same state under that lock. This unsynchronized access can cause the DMA channel to be left in an inconsistent state, recording a pause request on an already idle channel. Since no subsequent interrupt can clear this stale request, the channel becomes permanently wedged, rendering any device that relies on that DMA engine non‑functional. The impact is an availability breach that can affect kernel‑level operations dependent on that channel.

Affected Systems

All Linux kernel releases that include the dw‑edma driver are affected. Because no vendor‑specific version list is supplied, any system running a kernel with this driver may be vulnerable.

Risk and Exploitability

The EPSS score is reported as less than 1%, and the vulnerability is not listed in the CISA KEV catalog, indicating a low likelihood of exploitation in the wild. Exploitation requires precise timing between user‑initiated DMA requests and interrupt handling, which generally demands local kernel‑privileged access. The vulnerability’s impact on availability is high if triggered, but the overall threat level remains low to moderate under normal conditions.

Generated by OpenCVE AI on September 19, 2026 at 09:36 UTC.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Update the Linux kernel to a version that includes the dw‑edma race condition patch, selecting the latest stable release for your distribution.
  • If an immediate kernel upgrade is not possible, disable or remove the dw‑edma driver from the kernel configuration, or modify the device tree to prevent use of the affected DMA engine.
  • Actively monitor for hung DMA channels and trigger a reboot or graceful recovery when such a condition is detected.

Generated by OpenCVE AI on September 19, 2026 at 09:36 UTC.

Tracking

Sign in to view the affected projects.

Advisories
Source ID Title
Debian DLA Debian DLA DLA-4817-1 linux-6.12 security update
Debian DSA Debian DSA DSA-6528-1 linux security update
History

Sat, 19 Sep 2026 10:00:00 +0000

Type Values Removed Values Added
Weaknesses CWE-682

Thu, 17 Sep 2026 16:30:00 +0000

Type Values Removed Values Added
Description In the Linux kernel, the following vulnerability has been resolved: dmaengine: dw-edma: Serialize channel state checks pause() and resume() read and update channel state without holding vc.lock, while the interrupt handlers update the same state under it. Take the same lock around those state checks so that request, status, and configured stay consistent. For example, pause() can observe EDMA_ST_BUSY right before the interrupt handler completes the final descriptor and moves the channel to EDMA_ST_IDLE, and then record EDMA_REQ_PAUSE on an already idle channel. No further interrupt will acknowledge the request, and since issue_pending() requires EDMA_REQ_NONE, the channel is wedged for good: terminate_all() leaves the stale request behind, so even reconfiguring the channel does not recover it. issue_pending() already runs under vc.lock, but it tests configured before taking it. Move that test under the lock as well, so configured, request, and status are evaluated as one channel-state snapshot.
Title dmaengine: dw-edma: Serialize channel state checks
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-09-17T16:10:33.499Z

Reserved: 2026-09-17T15:57:05.657Z

Link: CVE-2026-93040

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Received

Published: 2026-09-17T17:17:57.117

Modified: 2026-09-17T17:17:57.117

Link: CVE-2026-93040

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-09-19T20:15:18Z

Weaknesses