CVE-2026-72474
In the Linux kernel, the following vulnerability has been resolved: …
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.
What to do now
- Check your exposureFind out whether the affected software runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Set the orderSystems that can be reached from the internet come first, then the rest.
References
- git.kernel.org/stable/c/65e82fa24965b2eb6ad9412f6c530ed9a50a625f
- git.kernel.org/stable/c/9e942c8579130e62734c14338e9f451780669164
- git.kernel.org/stable/c/a4f41ceecfe68e117bae9c76c5ebc5e2b353fa56
- git.kernel.org/stable/c/c0e6bb2b0408fcac6382158ee2bd9fdc45eceee9
- nvd.nist.gov/vuln/detail/CVE-2026-72474
- cve.org/CVERecord?id=CVE-2026-72474
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.