CVE-2026-72474
CVE CVE-2026-72474EUVD EUVD-2026-59373Published 2026-08-15T05:57:15.000ZLast changed 2026-08-17T05:15:23.000Z
What the advisory describes
In the Linux kernel, the following vulnerability has been resolved: dmaengine: dma-axi-dmac: use DMA pool to manange DMA descriptor For architectures like Microblaze or arm64 (where this IP is used), DMA_DIRECT_REMAP is set which means that dma_alloc_coherent() might remap (and hence vmalloc()) some memory. This became visible in a design where dma_direct_use_pool() is not possible. With the above, when calling dma_free_coherent(), vunmap() would be called from softirq context and thus leading to a BUG(). To fix it, use a dma pool that is allocated in .device_alloc_chan_resources() and allocate blocks from it. The key point is that now dma_pool_free() is used in axi_dmac_free_desc() to free the blocks and that just frees the blocks from the pool in the sense they can be used again. In other words, no actual call to dma_free_coherent() happens. That only happens when destroying the pool in axi_dmac_free_chan_resources() which does not happen in any interrupt context.
Source: EUVD (ENISA), in the words of the advisory.
Products the advisory names
These come from the advisory itself, not from any check we performed.
- Linux — Linux patch: 7.1.5; 6.8; patch: 7.2; 3f8fd25936ee5f52596f10d420f650c5b5e3285f <65e82fa24965b2eb6ad9412f6c530ed9a50a625f; 3f8fd25936ee5f52596f10d420f650c5b5e3285f <9e942c8579130e62734c14338e9f451780669164; patch: 6.12.97; 3f8fd25936ee5f52596f10d420f650c5b5e3285f <a4f41ceecfe68e117bae9c76c5ebc5e2b353fa56; patch: 0; 3f8fd25936ee5f52596f10d420f650c5b5e3285f <c0e6bb2b0408fcac6382158ee2bd9fdc45eceee9; patch: 6.18.40
The versions shown are the advisory's own. Patchlage compares no version numbers and derives no judgement from them — which version is installed is something a person has to look up.
Carried in the product catalogue
An estate covering these products can be recorded in Patchlage. An advisory about them appears in the next morning's situation report.
- Linux — Linux
Does this concern one of your customers?
This page cannot answer that — it does not know your estate. Whoever has recorded their environments gets the answer the morning after publication, together with a paragraph they can forward to the customer unedited.
Try it for 28 daysPatchlage reports hits and suspected hits. About everything else this system says nothing — neither this page nor the situation report ever claims that an estate is safe.