CVE-2026-93040

dmaengine: dw-edma: Serialize channel state checks

N/A
Published: September 17, 2026 at 04:10 PM UTC
Updated: October 19, 2026 at 10:16 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

5.3e63d79d1ffcd2201a2dbff1d7a1184b8f3ec74cf
Vendor states this is fixed in 2d76b91deeab973dd8a8c2ee587ce27f881de768 (fixed)
Vendor states this is fixed in 3001cfcee30dcc81f8b3774319c12067f126e49a (fixed)
Vendor states this is fixed in 6fc436e1500c5e4f0dde2a3dbadf6d898057be8f (fixed)
Vendor states this is fixed in b6293a8a38f4d5866ce1a264c138265a02e4c53a (fixed)
Vendor states this is fixed in be0072af8ce6e9458cc586e0e8b41a251e7d4316 (fixed)
Vendor states this is fixed in da16a02f0998a0d455ce6265b836b29ad92e6e58 (fixed)
Vendor states this is fixed in f7d1619f3e10c619b62c6cd6d95371b5c526c85a (fixed)
Vendor states this is fixed in fe0ffa0190e862ed71e8c1a476090f648c9cb7d9 (fixed)
Vendor states this is fixed in 5.10.270 (unaffected)
Vendor states this is fixed in 5.15.221 (unaffected)
Vendor states this is fixed in 5.3 (unaffected)
Vendor states this is fixed in 6.1.188 (unaffected)
Vendor states this is fixed in 6.12.110 (unaffected)
Vendor states this is fixed in 6.18.52 (unaffected)
Vendor states this is fixed in 6.6.157 (unaffected)
Vendor states this is fixed in 7.2.6 (unaffected)
Vendor states this is fixed in 7.3 (unaffected)
Vendor states this is fixed in 7.3-rc1 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card