Local service interruption via incorrect DMA synchronization
Published May 27, 2026 · Updated May 27, 2026
Improper DMA synchronization in the Linux Kernel Atmel TDES driver allows local users to interrupt service through stale output data. In drivers/crypto/atmel-tdes.c, the completion path synchronizes dma_addr_out for the device rather than the CPU before consuming DMA output, allowing non-coherent caches to return stale data. The driver must process TDES output on a non-coherent platform; the documented impact is limited to availability, with no confidentiality or integrity loss.
Summary
What happened
Improper DMA synchronization in the Linux Kernel Atmel TDES driver allows local users to interrupt service through stale output data. In drivers/crypto/atmel-tdes.c, the completion path synchronizes dma_addr_out for the device rather than the CPU before consuming DMA output, allowing non-coherent caches to return stale data. The driver must process TDES output on a non-coherent platform; the documented impact is limited to availability, with no confidentiality or integrity loss.
The record
- CVE
- CVE-2026-46077
- Published
- May 27, 2026
- Updated
- May 27, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- May 27, 2026CVE publishedPublication date reported by the CVE source.
- May 27, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=13802005d8f2db244ec1f5d7f6923de8f7a463db <12a0adfe498cd5d87e6365d7ca5f6b3eed79e523
- Affected versionversion=13802005d8f2db244ec1f5d7f6923de8f7a463db <5281e6e2302362f6b75b70cbfe4098d2a25dafd9
- Affected versionversion=13802005d8f2db244ec1f5d7f6923de8f7a463db <863d11b3927703ad95077c81a8a6489c5c7872f7
- Affected versionversion=13802005d8f2db244ec1f5d7f6923de8f7a463db <b5f5df801d161ba244f391519cbff2f4e5c6edc2
- Affected versionversion=13802005d8f2db244ec1f5d7f6923de8f7a463db <c8a9a647532f5c2a04180352693215e24e9dba03
- Affected versionversion=3.6
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo