dmaengine: dw-edma: Serialize channel state checks
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 5.10.270, 5.15.221, 6.1.188, 6.6.157, 6.12.110, and 2 more
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
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.
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
From e63d79d1ffcd2201a2dbff1d7a1184b8f3ec74cf · fixed in be0072af8ce6e9458cc586e0e8b41a251e7d4316; From e63d79d1ffcd2201a2dbff1d7a1184b8f3ec74cf · fixed in 2d76b91deeab973dd8a8c2ee587ce27f881de768; From e63d79d1ffcd2201a2dbff1d7a1184b8f3ec74cf · fixed in 3001cfcee30dcc81f8b3774319c12067f126e49a; From e63d79d1ffcd2201a2dbff1d7a1184b8f3ec74cf · fixed in b6293a8a38f4d5866ce1a264c138265a02e4c53a; From e63d79d1ffcd2201a2dbff1d7a1184b8f3ec74cf · fixed in da16a02f0998a0d455ce6265b836b29ad92e6e58; From e63d79d1ffcd2201a2dbff1d7a1184b8f3ec74cf · fixed in fe0ffa0190e862ed71e8c1a476090f648c9cb7d9; From e63d79d1ffcd2201a2dbff1d7a1184b8f3ec74cf · fixed in 6fc436e1500c5e4f0dde2a3dbadf6d898057be8f; From e63d79d1ffcd2201a2dbff1d7a1184b8f3ec74cf · fixed in f7d1619f3e10c619b62c6cd6d95371b5c526c85a
- Linux Linux
5.3
- KernelLinux
From 5.3.0 · fixed in 5.10.270; From 5.11.0 · fixed in 5.15.221; From 5.16.0 · fixed in 6.1.188; From 6.2.0 · fixed in 6.6.157; From 6.7.0 · fixed in 6.12.110; From 6.13.0 · fixed in 6.18.52; From 6.19.0 · fixed in 7.2.6
References 8
git.kernel.org
- stable/c/be0072af8ce6e9458cc586e0e8b41a251e7d4316
- stable/c/2d76b91deeab973dd8a8c2ee587ce27f881de768
- stable/c/3001cfcee30dcc81f8b3774319c12067f126e49a
- stable/c/b6293a8a38f4d5866ce1a264c138265a02e4c53a
- stable/c/da16a02f0998a0d455ce6265b836b29ad92e6e58
- stable/c/fe0ffa0190e862ed71e8c1a476090f648c9cb7d9
- stable/c/6fc436e1500c5e4f0dde2a3dbadf6d898057be8f
- stable/c/f7d1619f3e10c619b62c6cd6d95371b5c526c85a