CVE-2026-46077

crypto: atmel-tdes - fix DMA sync direction

MEDIUM

5.5

CVSS Score

Published: May 27, 2026 at 12:58 PM UTC

Updated: June 27, 2026 at 11:41 AM UTC

1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available

Start Free Sign In

Severity

MEDIUM5.5

Exploit prediction

EPSS 0.1%

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

Linux Kernel · Linux

95%

3.6 ≤ v < 5.10.2583.6 ≤ v < 5.15.2093.6 ≤ v < 6.1.1753.6 ≤ v < 6.12.863.6 ≤ v < 6.18.273.6 ≤ v < 6.6.1403.6 ≤ v < 7.0.43.6 ≤ v < 7.15.11 ≤ v < 5.15.2095.16 ≤ v < 6.1.1756.13 ≤ v < 6.18.276.19 ≤ v < 7.0.46.2 ≤ v < 6.6.1406.7 ≤ v < 6.12.8613802005d8f2db244ec1f5d7f6923de8f7a463db3.6

Vendor states this is fixed in 12a0adfe498cd5d87e6365d7ca5f6b3eed79e523 (fixed)

Vendor states this is fixed in 5281e6e2302362f6b75b70cbfe4098d2a25dafd9 (fixed)

Vendor states this is fixed in 863d11b3927703ad95077c81a8a6489c5c7872f7 (fixed)

Vendor states this is fixed in b5f5df801d161ba244f391519cbff2f4e5c6edc2 (fixed)

Vendor states this is fixed in b9b28f3881dd514e74f98ae04e79a635022a4804 (fixed)

Vendor states this is fixed in c0f3002c02a3a83250e25582ffbe8df7eb78a8bd (fixed)

Vendor states this is fixed in c8a9a647532f5c2a04180352693215e24e9dba03 (fixed)

Vendor states this is fixed in ce3224678acb8c0b3473daa7d7dbffc998c6951a (fixed)

Vendor states this is fixed in 3.6 (unaffected)

Vendor states this is fixed in 5.10.258 (unaffected)

Vendor states this is fixed in 5.15.209 (unaffected)

Vendor states this is fixed in 6.1.175 (unaffected)