CVE-2026-90387 swiotlb: Preserve allocation virtual address for dynamic pools
Incorrect virtual address handling in Linux kernel swiotlb dynamic pools can cause memory free failures, potentially leading to system crashes.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Local or same network only
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2026-90387?
CVE-2026-90387 is a high-severity vulnerability in Linux, published on 17 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Official 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.
Which versions are affected by CVE-2026-90387?
How do I fix CVE-2026-90387?
Apply the vendor's patch.
Is CVE-2026-90387 being exploited?
There is no known exploitation of CVE-2026-90387 in the wild and no public exploit code.
Sources
Also known as AZL-102470, BELL-CVE-2026-90387, DEBIAN-CVE-2026-90387, GHSA-rw87-3jgx-gg57, UBUNTU-CVE-2026-90387.