dmaengine: dw-edma: Serialize channel state checks
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel fe0ffa0190e862ed71e8c1a476090f648c9cb7d9, Kernel 2d76b91deeab973dd8a8c2ee587ce27f881de768, Kernel 3001cfcee30dcc81f8b3774319c12067f126e49a and 12 more.
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
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | >=e63d79d1ffcd2201a2dbff1d7a1184b8f3ec74cf <fe0ffa0190e862ed71e8c1a476090f648c9cb7d9, >=e63d79d1ffcd2201a2dbff1d7a1184b8f3ec74cf <2d76b91deeab973dd8a8c2ee587ce27f881de768, >=e63d79d1ffcd2201a2dbff1d7a1184b8f3ec74cf <3001cfcee30dcc81f8b3774319c12067f126e49a, >=e63d79d1ffcd2201a2dbff1d7a1184b8f3ec74cf <6fc436e1500c5e4f0dde2a3dbadf6d898057be8f, >=e63d79d1ffcd2201a2dbff1d7a1184b8f3ec74cf <b6293a8a38f4d5866ce1a264c138265a02e4c53a, >=e63d79d1ffcd2201a2dbff1d7a1184b8f3ec74cf <be0072af8ce6e9458cc586e0e8b41a251e7d4316, >=e63d79d1ffcd2201a2dbff1d7a1184b8f3ec74cf <da16a02f0998a0d455ce6265b836b29ad92e6e58, >=e63d79d1ffcd2201a2dbff1d7a1184b8f3ec74cf <f7d1619f3e10c619b62c6cd6d95371b5c526c85a, =5.3 | fe0ffa0190e862ed71e8c1a476090f648c9cb7d9, 2d76b91deeab973dd8a8c2ee587ce27f881de768, 3001cfcee30dcc81f8b3774319c12067f126e49a, 6fc436e1500c5e4f0dde2a3dbadf6d898057be8f, b6293a8a38f4d5866ce1a264c138265a02e4c53a, be0072af8ce6e9458cc586e0e8b41a251e7d4316, da16a02f0998a0d455ce6265b836b29ad92e6e58, f7d1619f3e10c619b62c6cd6d95371b5c526c85a |
| linux-kernel: Kernel | >=5.16.0 <6.1.188, >=5.3.0 <5.10.270, >=6.13.0 <6.18.52, >=6.19.0 <7.2.6, >=6.2.0 <6.6.157, >=6.7.0 <6.12.110, >=5.11.0 <5.15.221 | 6.1.188, 5.10.270, 6.18.52, 7.2.6, 6.6.157, 6.12.110, 5.15.221 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket