dma: fix call order in dmam_free_coherent
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 9ac7849e35f705830f7b016ff272b0ff1f7ff759 · < 1fe97f68fce1ba24bf823bfb0eb0956003473130| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
dma: fix call order in dmam_free_coherent
dmam_free_coherent() frees a DMA allocation, which makes the freed vaddr available for reuse, then calls devres_destroy() to remove and free the data structure used to track the DMA allocation. Between the two calls, it is possible for a concurrent task to make an allocation with the same vaddr and add it to the devres list.
If this happens, there will be two entries in the devres list with the same vaddr and devres_destroy() can free the wrong entry, triggering the WARN_ON() in dmam_match.
Fix by destroying the devres entry before freeing the DMA allocation.
kokonut //net/encryption http://sponge2/b9145fe6-0f72-4325-ac2f-a84d81075b03
From the CVE record · Linux
The Linux kernel’s dmam_free_coherent() frees a DMA allocation before removing its tracking entry. If a concurrent task reuses the same virtual address, devres_destroy() can remove the wrong entry and trigger a warning. The input does not specify an attack path, authentication requirement, or user interaction.
Engineers running Linux kernels should check whether their builds include the affected dmam_free_coherent() implementation; affected versions were not provided.