crypto: atmel-tdes - fix DMA sync direction
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 13802005d8f2db244ec1f5d7f6923de8f7a463db · < 863d11b3927703ad95077c81a8a6489c5c7872f7| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
crypto: atmel-tdes - fix DMA sync direction
Before DMA output is consumed by the CPU, ->dma_addr_out must be synced with dma_sync_single_for_cpu() instead of dma_sync_single_for_device(). Using the wrong direction can return stale cache data on non-coherent platforms.
From the CVE record · Linux
The Linux kernel’s atmel-tdes crypto driver uses the wrong DMA synchronization direction before the CPU consumes output. On non-coherent platforms, this can return stale cache data. The input does not specify an attacker path, authentication requirement, or user interaction.
Engineers running Linux kernels with the atmel-tdes driver on non-coherent platforms should check their versions; affected versions are not specified.