CVE-2026-46077
Published May 27, 2026
Modified May 27, 2026
Description
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.
References
Other References
https://git.kernel.org/stable/c/12a0adfe498cd5d87e6365d7ca5f6b3eed79e523
https://git.kernel.org/stable/c/5281e6e2302362f6b75b70cbfe4098d2a25dafd9
https://git.kernel.org/stable/c/863d11b3927703ad95077c81a8a6489c5c7872f7
https://git.kernel.org/stable/c/b5f5df801d161ba244f391519cbff2f4e5c6edc2
https://git.kernel.org/stable/c/c8a9a647532f5c2a04180352693215e24e9dba03
Frequently Asked Questions
What is CVE-2026-46077? +
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.
How do I check if I'm vulnerable to CVE-2026-46077? +
You can use Secably's free Website Scanner to check your website for known vulnerabilities. For infrastructure scanning, use the Port Scanner to identify exposed services that may be affected. Check the vendor advisories linked above for specific patch and version information.