crypto: iaa - unmap dst before software fallback on decompress
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
crypto: iaa - unmap dst before software fallback on decompress
On a hardware analytics error, decompress retries through the software fallback, which writes req->dst with the CPU while it is still mapped DMA_FROM_DEVICE. With SWIOTLB active the later dma_unmap_sg() copies the stale bounce buffer over req->dst, corrupting the result.
Unmap before the fallback runs. The async path unmaps inline; the sync path signals the retry with -EAGAIN so iaa_comp_adecompress() runs the fallback after unmapping.
From the CVE record · Linux
The Linux kernel's crypto iaa decompression path can corrupt a result when a hardware analytics error triggers software fallback while the destination remains DMA-mapped and SWIOTLB is active. The input does not establish whether an attacker can trigger this condition, or specify network access, authentication, or user-interaction requirements.
Teams running Linux kernels with the crypto iaa decompression path should check whether their kernel is affected; no affected versions are specified.