CVE-2026-93042

High

Description

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.

SeverityHigh
CVSS8.8
Exploit probability—
ProductLinux
PublishedSep 17, 2026
First seenSep 17, 2026

How to fix

Update
  • Linux Linuxda56839aced48ecb70033962d7ea98f55b0c5656, 65e387b95d3855aa894ac729e1778e5bcb9083cb, 4793f9099a1cadf4e37f3a03d524af6bce88a0ea, be87d86537de7ea6fd025f41033d2faff880973f, f3ec6702a1d216be61f692cc0a983d6c8fb5ebf7, 99109a51efd28c9a661fbfb9469b023c517b31d1 or later

Affected products

ProductAffected versionsFixed in
Linux Linuxe63d79d1ffcd2201a2dbff1d7a1184b8f3ec74cf ≤ v < da56839aced48ecb70033962d7ea98f55b0c5656, e63d79d1ffcd2201a2dbff1d7a1184b8f3ec74cf ≤ v < 65e387b95d3855aa894ac729e1778e5bcb9083cb, e63d79d1ffcd2201a2dbff1d7a1184b8f3ec74cf ≤ v < 4793f9099a1cadf4e37f3a03d524af6bce88a0ea, e63d79d1ffcd2201a2dbff1d7a1184b8f3ec74cf ≤ v < be87d86537de7ea6fd025f41033d2faff880973f, e63d79d1ffcd2201a2dbff1d7a1184b8f3ec74cf ≤ v < f3ec6702a1d216be61f692cc0a983d6c8fb5ebf7, e63d79d1ffcd2201a2dbff1d7a1184b8f3ec74cf ≤ v < 99109a51efd28c9a661fbfb9469b023c517b31d1, 5.3da56839aced48ecb70033962d7ea98f55b0c5656, 65e387b95d3855aa894ac729e1778e5bcb9083cb, 4793f9099a1cadf4e37f3a03d524af6bce88a0ea, be87d86537de7ea6fd025f41033d2faff880973f, f3ec6702a1d216be61f692cc0a983d6c8fb5ebf7, 99109a51efd28c9a661fbfb9469b023c517b31d1

Check your version

Choose the product and enter the version you run to see whether it falls in the affected range.

In the Intelligence 360 plan

Attack Surface Management

See the assets tied to your domains, the technologies they run and known vulnerabilities in one list.