Strix
63.5K

CVE-2026-93040

Unknown

Last modified

CVE-2026-93040 is a vulnerability of currently unknown severity. 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.

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 Software

Source: CNA advisory (CVE.org). NVD analysis pending.

VendorProductVersions
LinuxLinux>= e63d79d1ffcd2201a2dbff1d7a1184b8f3ec74cf, < be0072af8ce6e9458cc586e0e8b41a251e7d4316; >= e63d79d1ffcd2201a2dbff1d7a1184b8f3ec74cf, < 2d76b91deeab973dd8a8c2ee587ce27f881de768; >= e63d79d1ffcd2201a2dbff1d7a1184b8f3ec74cf, < 3001cfcee30dcc81f8b3774319c12067f126e49a; >= e63d79d1ffcd2201a2dbff1d7a1184b8f3ec74cf, < b6293a8a38f4d5866ce1a264c138265a02e4c53a; >= e63d79d1ffcd2201a2dbff1d7a1184b8f3ec74cf, < da16a02f0998a0d455ce6265b836b29ad92e6e58; >= e63d79d1ffcd2201a2dbff1d7a1184b8f3ec74cf, < fe0ffa0190e862ed71e8c1a476090f648c9cb7d9; >= e63d79d1ffcd2201a2dbff1d7a1184b8f3ec74cf, < 6fc436e1500c5e4f0dde2a3dbadf6d898057be8f; >= e63d79d1ffcd2201a2dbff1d7a1184b8f3ec74cf, < f7d1619f3e10c619b62c6cd6d95371b5c526c85a
LinuxLinux5.3

References

Timeline

Published
Last Modified
Status
Received

Frequently Asked Questions

What is CVE-2026-93040?
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.
How severe is CVE-2026-93040?
Severity scoring for CVE-2026-93040 is pending analysis.
How do I fix CVE-2026-93040?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

How Strix Helps

Related CVEs from 2026

View all 2026CVEs →

Are you affected by CVE-2026-93040?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST