Microsoft · crypto: atmel-tdes - fix DMA sync direction
Affects MicrosoftSource GCVE Database
Not known to be exploited.
Data as of 30 Oct 2026, 11:52 UTC
Rated by Threat Radar · No CVSS score from NVD or the CNA
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 2% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Exploitation evidence
Disclosed: evidence found.
CVE published 2 May 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Microsoft Security Response Center Microsoft | Affected
| Fixed in– |
AI-suggested
No specific mitigation or workaround information is available at this time.
Description
CVE-2026-46077 is a vulnerability related to the 'crypto: atmel-tdes' component involving a fix for DMA synchronization direction. The available information does not provide technical details about the nature of the vulnerability or its exploitation. There is no CVSS score or detailed impact description. No known exploits are reported in the wild, and no patch or remediation details are provided. The affected products include Microsoft and Azure Linux 3.0 versions. Due to the lack of detailed information, the severity is assessed as medium based on the potential for cryptographic component issues to impact system security.