dmaengine: Fix possible use after free
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 0f571515c332e00b3515dbe0859ceaa30ab66e00 · < 329ec20a86091d2a6e5b4fe507545e7d678a22a2| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
dmaengine: Fix possible use after free
In dma_release_channel(), check chan->device->privatecnt after call dma_chan_put(). However, dma_chan_put() call dma_device_put() which could release the last reference of the device if the DMA provider is already gone and hence free it.
Fixes it by moving dma_chan_put() after the check.
From the CVE record · Linux
The Linux kernel's dmaengine code can access a freed DMA device in dma_release_channel() if the DMA provider is already gone. The input does not specify what an attacker could do or whether exploitation requires network access, authentication, or user interaction.
Engineers running the Linux kernel should check their deployments; affected versions are not specified.