CVE-2026-46077
Awaiting Analysis Awaiting Analysis - Queue
crypto: atmel-tdes DMA sync direction vulnerability in Linux kernel

Publication date: 2026-05-27

Last updated on: 2026-06-01

Assigner: kernel.org

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.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-05-27
Last Modified
2026-06-01
Generated
2026-06-16
AI Q&A
2026-05-27
EPSS Evaluated
2026-06-15
NVD
CVE-2026-46077
EUVD
EUVD-2026-32459
Affected Vendors & Products
Showing 2 associated CPEs
Vendor Product Version / Range
linux_kernel linux_kernel *
linux linux_kernel *
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-UNKNOWN
Attack-Flow Graph
AI Quick Actions
Instant insights powered by AI
Executive Summary

This vulnerability exists in the Linux kernel's crypto subsystem, specifically in the atmel-tdes driver. It involves an incorrect use of DMA (Direct Memory Access) synchronization functions. Before the CPU consumes DMA output, the dma_addr_out must be synchronized using dma_sync_single_for_cpu(), but the code incorrectly uses dma_sync_single_for_device().

Using the wrong synchronization direction can cause the CPU to read stale cache data on platforms where the cache is not coherent, potentially leading to incorrect or outdated data being processed.

Impact Analysis

The impact of this vulnerability is that the CPU might consume stale or outdated data due to improper DMA synchronization. On non-coherent platforms, this can lead to incorrect cryptographic operations or data processing errors, which may affect system reliability or security.

Chat Assistant
Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-46077. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70
EPSS Chart