dma: fix call order in dmam_free_coherent

jira LE-2157
cve CVE-2024-43856
Rebuild_History Non-Buildable kernel-5.14.0-503.14.1.el9_5
commit-author Lance Richardson <[email protected]>
commit 28e8b74

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.

Tested:
  kokonut //net/encryption
    http://sponge2/b9145fe6-0f72-4325-ac2f-a84d81075b03

Fixes: 9ac7849 ("devres: device resource management")
	Signed-off-by: Lance Richardson <[email protected]>
	Signed-off-by: Christoph Hellwig <[email protected]>
(cherry picked from commit 28e8b74)
	Signed-off-by: Jonathan Maple <[email protected]>

Author: PlaidCat

kernel/dma/mapping.c

@@ -67,8 +67,8 @@ void dmam_free_coherent(struct device *dev, size_t size, void *vaddr,
 {
 	struct dma_devres match_data = { size, vaddr, dma_handle };
 
-	dma_free_coherent(dev, size, vaddr, dma_handle);
 	WARN_ON(devres_destroy(dev, dmam_release, dmam_match, &match_data));
+	dma_free_coherent(dev, size, vaddr, dma_handle);
 }
 EXPORT_SYMBOL(dmam_free_coherent);