dmaengine: dw-edma: Terminate all descriptors without callbacks
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel f3ec6702a1d216be61f692cc0a983d6c8fb5ebf7, Kernel 4793f9099a1cadf4e37f3a03d524af6bce88a0ea, Kernel 65e387b95d3855aa894ac729e1778e5bcb9083cb and 8 more.
In the Linux kernel, the following vulnerability has been resolved: dmaengine: dw-edma: Terminate all descriptors without callbacks The DMA Engine client documentation says in the "Terminate APIs" section of Documentation/driver-api/dmaengine/client.rst: "No callback functions will be called for any incomplete transfers." dw-edma instead calls vchan_cookie_complete() when a deferred STOP reaches the interrupt handler. This schedules a callback for the active descriptor and leaves other issued or submitted descriptors queued. A late callback after dmaengine_terminate_sync() can dereference client state that has already been freed, while leftover descriptors may later restart into reused buffers or leak. Move all issued and submitted descriptors to the terminated list whenever termination completes. For a pending STOP, do this from both the DONE and ABORT paths. Complete their cookies in order without scheduling callbacks. A STOP can remain pending until the running transfer raises an interrupt. Make device_synchronize() wait for such a pending STOP to complete before releasing terminated descriptors. Reuse it from free_chan_resources(), then release the remaining virt-dma resources. Sleep instead of busy-polling while waiting, and warn if the existing timeout expires.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | >=e63d79d1ffcd2201a2dbff1d7a1184b8f3ec74cf <f3ec6702a1d216be61f692cc0a983d6c8fb5ebf7, >=e63d79d1ffcd2201a2dbff1d7a1184b8f3ec74cf <4793f9099a1cadf4e37f3a03d524af6bce88a0ea, >=e63d79d1ffcd2201a2dbff1d7a1184b8f3ec74cf <65e387b95d3855aa894ac729e1778e5bcb9083cb, >=e63d79d1ffcd2201a2dbff1d7a1184b8f3ec74cf <99109a51efd28c9a661fbfb9469b023c517b31d1, >=e63d79d1ffcd2201a2dbff1d7a1184b8f3ec74cf <be87d86537de7ea6fd025f41033d2faff880973f, >=e63d79d1ffcd2201a2dbff1d7a1184b8f3ec74cf <da56839aced48ecb70033962d7ea98f55b0c5656, =5.3 | f3ec6702a1d216be61f692cc0a983d6c8fb5ebf7, 4793f9099a1cadf4e37f3a03d524af6bce88a0ea, 65e387b95d3855aa894ac729e1778e5bcb9083cb, 99109a51efd28c9a661fbfb9469b023c517b31d1, be87d86537de7ea6fd025f41033d2faff880973f, da56839aced48ecb70033962d7ea98f55b0c5656 |
| linux-kernel: Kernel | >=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.3.0 <6.1.191 | 6.18.52, 7.2.6, 6.6.157, 6.12.110, 6.1.191 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket