iommu/dma: Check atomic pool allocation result directly
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 9420139f516d7fbc248ce17f35275cb005ed98ea · < fb0b39287ba894dbdfac2901c51788b63f5c2291| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
iommu/dma: Check atomic pool allocation result directly
The non-blocking, non-coherent allocation path uses dma_alloc_from_pool(), which returns the allocated page and fills cpu_addr only on success.
Do not rely on cpu_addr to detect allocation failure in this path. Check the returned page directly before using it for the IOMMU mapping.
From the CVE record · Linux
The Linux kernel’s non-blocking, non-coherent DMA allocation path can fail to detect when pool allocation returns no page before attempting an IOMMU mapping. The input does not specify what an attacker could achieve or whether exploitation requires network access, local access, authentication, or user interaction.
Engineers running the Linux kernel should check their versions; the affected versions are not specified.