Answer in brief
CVE-2026-46077 records a Medium severity (CVSS 5.5) vulnerability in crypto: atmel-tdes - fix DMA sync direction. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
Answer in brief
CVE-2026-46077 records a Medium severity (CVSS 5.5) vulnerability in crypto: atmel-tdes - fix DMA sync direction. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 5.5. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=13802005d8f2db244ec1f5d7f6923de8f7a463db <ce3224678acb8c0b3473daa7d7dbffc998c6951a || >=13802005d8f2db244ec1f5d7f6923de8f7a463db <b9b28f3881dd514e74f98ae04e79a635022a4804 || >=13802005d8f2db244ec1f5d7f6923de8f7a463db <c0f3002c02a3a83250e25582ffbe8df7eb78a8bd || >=13802005d8f2db244ec1f5d7f6923de8f7a463db <5281e6e2302362f6b75b70cbfe4098d2a25dafd9 || >=13802005d8f2db244ec1f5d7f6923de8f7a463db <12a0adfe498cd5d87e6365d7ca5f6b3eed79e523 || >=13802005d8f2db244ec1f5d7f6923de8f7a463db <863d11b3927703ad95077c81a8a6489c5c7872f7 || >=13802005d8f2db244ec1f5d7f6923de8f7a463db <b5f5df801d161ba244f391519cbff2f4e5c6edc2 || >=13802005d8f2db244ec1f5d7f6923de8f7a463db <c8a9a647532f5c2a04180352693215e24e9dba03 | ce3224678acb8c0b3473daa7d7dbffc998c6951a, b9b28f3881dd514e74f98ae04e79a635022a4804, c0f3002c02a3a83250e25582ffbe8df7eb78a8bd, 5281e6e2302362f6b75b70cbfe4098d2a25dafd9, 12a0adfe498cd5d87e6365d7ca5f6b3eed79e523, 863d11b3927703ad95077c81a8a6489c5c7872f7, b5f5df801d161ba244f391519cbff2f4e5c6edc2, c8a9a647532f5c2a04180352693215e24e9dba03 |
| Linux/Linuxgeneric | 3.6 | Not reported |
Published upstream
May 27, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Jun 24, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Jun 24, 2026
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.
Quoted source text, attributed separately from HOL analysis.
CVSS is 5.5. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=13802005d8f2db244ec1f5d7f6923de8f7a463db <ce3224678acb8c0b3473daa7d7dbffc998c6951a || >=13802005d8f2db244ec1f5d7f6923de8f7a463db <b9b28f3881dd514e74f98ae04e79a635022a4804 || >=13802005d8f2db244ec1f5d7f6923de8f7a463db <c0f3002c02a3a83250e25582ffbe8df7eb78a8bd || >=13802005d8f2db244ec1f5d7f6923de8f7a463db <5281e6e2302362f6b75b70cbfe4098d2a25dafd9 || >=13802005d8f2db244ec1f5d7f6923de8f7a463db <12a0adfe498cd5d87e6365d7ca5f6b3eed79e523 || >=13802005d8f2db244ec1f5d7f6923de8f7a463db <863d11b3927703ad95077c81a8a6489c5c7872f7 || >=13802005d8f2db244ec1f5d7f6923de8f7a463db <b5f5df801d161ba244f391519cbff2f4e5c6edc2 || >=13802005d8f2db244ec1f5d7f6923de8f7a463db <c8a9a647532f5c2a04180352693215e24e9dba03 | ce3224678acb8c0b3473daa7d7dbffc998c6951a, b9b28f3881dd514e74f98ae04e79a635022a4804, c0f3002c02a3a83250e25582ffbe8df7eb78a8bd, 5281e6e2302362f6b75b70cbfe4098d2a25dafd9, 12a0adfe498cd5d87e6365d7ca5f6b3eed79e523, 863d11b3927703ad95077c81a8a6489c5c7872f7, b5f5df801d161ba244f391519cbff2f4e5c6edc2, c8a9a647532f5c2a04180352693215e24e9dba03 |
| Linux/Linuxgeneric | 3.6 | Not reported |
Published upstream
May 27, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Jun 24, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Jun 24, 2026
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.
Quoted source text, attributed separately from HOL analysis.