Description
In the Linux kernel, the following vulnerability has been resolved: swiotlb: Preserve allocation virtual address for dynamic pools swiotlb_alloc_tlb() can allocate from the DMA atomic pool when a decrypted pool is needed from atomic context. With CONFIG_DMA_DIRECT_REMAP, the atomic pool is backed by remapped virtual addresses, which are not the same as the direct-map addresses returned by phys_to_virt(). swiotlb_init_io_tlb_pool() currently reconstructs the pool virtual address from the physical start address. For atomic-pool backed allocations this stores the wrong address in pool->vaddr. Later, swiotlb_free_tlb() passes that address to dma_free_from_pool(), which will fail to recognize the chunk Pass the virtual address returned by the allocation path into swiotlb_init_io_tlb_pool(), and store that address in pool->vaddr. This keeps the pool free path using the same virtual address as the allocator.
References5
- git.kernel.org/stable/c/35e0103177826430b5df888b1506239d41e76ab5
- git.kernel.org/stable/c/45507dcb0847e96add4455274b12df0eca6590b4
- git.kernel.org/stable/c/57d29044d0f29a76c6ec0c112c8c7371d5608dc7
- git.kernel.org/stable/c/68bf3ebd8e7020dae58e8aa14c7d482738bff9a8
- git.kernel.org/stable/c/c1f4d7763cdf1b9e0d35c14aa6f52d0512a36319
Metrics
- CVSS 3.1
-
7.8
HIGH
Score source: CNA
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H - EPSS — exploit probability
- 0% percentile: 6 · as of 8 November 2026
Could this be exploited in your environment?
A patch closes the known hole. A penetration test shows what an attacker can still reach — with proof.