dmaengine: dw-edma: Terminate all descriptors without callbacks
- 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 6.6.157, 6.12.110, 6.18.52, 7.2.6
- 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: 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.
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
From e63d79d1ffcd2201a2dbff1d7a1184b8f3ec74cf · fixed in 65e387b95d3855aa894ac729e1778e5bcb9083cb; From e63d79d1ffcd2201a2dbff1d7a1184b8f3ec74cf · fixed in 4793f9099a1cadf4e37f3a03d524af6bce88a0ea; From e63d79d1ffcd2201a2dbff1d7a1184b8f3ec74cf · fixed in be87d86537de7ea6fd025f41033d2faff880973f; From e63d79d1ffcd2201a2dbff1d7a1184b8f3ec74cf · fixed in f3ec6702a1d216be61f692cc0a983d6c8fb5ebf7; From e63d79d1ffcd2201a2dbff1d7a1184b8f3ec74cf · fixed in 99109a51efd28c9a661fbfb9469b023c517b31d1
- Linux Linux
5.3
- KernelLinux
From 5.3.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