CVE-2026-64590

UNRATEDCVSS · not yet scoredTrending — 5 sources updated this week
—
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • No CVSS published and no exploitation signals yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS v2: —Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

In the Linux kernel, the following vulnerability has been resolved:

dma-buf/udmabuf: skip redundant cpu sync to fix cacheline EEXIST warning

When CONFIG_DMA_API_DEBUG_SG is enabled, importing a udmabuf into a DRM driver (e.g. amdgpu for video playback in GNOME Videos / Showtime) triggers a spurious warning:

DMA-API: amdgpu 0000:03:00.0: cacheline tracking EEXIST, \ overlapping mappings aren't supported WARNING: kernel/dma/debug.c:619 at add_dma_entry+0x473/0x5f0

The call chain is:

amdgpu_cs_ioctl -> amdgpu_ttm_backend_bind -> dma_buf_map_attachment -> [udmabuf] map_udmabuf -> get_sg_table -> dma_map_sgtable(dev, sg, direction, 0) // attrs=0 -> debug_dma_map_sg -> add_dma_entry -> EEXIST

This happens because udmabuf builds a per-page scatter-gather list via sg_set_folio(). When begin_cpu_udmabuf() has already created an sg table mapped for the misc device, and an importer such as amdgpu maps the same pages for its own device via map_udmabuf(), the DMA debug infrastructure sees two active mappings whose physical addresses share cacheline boundaries and warns about the overlap.

The DMA_ATTR_SKIP_CPU_SYNC flag suppresses this check in add_dma_entry() because it signals that no CPU cache maintenance is performed at map/unmap time, making the cacheline overlap harmless.

All other major dma-buf exporters already pass this flag:

  • drm_gem_map_dma_buf() passes DMA_ATTR_SKIP_CPU_SYNC
  • amdgpu_dma_buf_map() passes DMA_ATTR_SKIP_CPU_SYNC

The CPU sync at map/unmap time is also redundant for udmabuf: begin_cpu_udmabuf() and end_cpu_udmabuf() already perform explicit cache synchronization via dma_sync_sgtable_for_cpu/device() when CPU access is requested through the dma-buf interface.

Pass DMA_ATTR_SKIP_CPU_SYNC to dma_map_sgtable() and dma_unmap_sgtable() in udmabuf to suppress the spurious warning and skip the redundant sync.

CVSS v3
—
EchelonGraph score
Not yet assessedNo source has published severity data for this CVE yet — no CVSS score from NVD or a CNA, no GitHub advisory, and it is not in CISA KEV. This is not a rating of zero; we cannot assess it yet.
EG Score
—
EG Risk
—
EPSS PROB
0%
EPSS %ILE
5%
KEV
Not listed

Published

August 6, 2026

Last Modified

August 17, 2026

References (5)

Vendor Advisories for CVE-2026-64590(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(5 across 4 ecosystems)
Debian:12(2)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 7.2~rc5-1~exp1 (338 versions)——
linux-6.12—6.12.100-1~deb12u1—
Debian:11(1)
PackageVulnerable rangeFixed inDependents
linux5.10.103-1 ... 7.2~rc5-1~exp1 (500 versions)——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.95-1~bpo12+1 (30 versions)6.12.96-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.1~rc7-1~exp1 (156 versions)7.1.4-1—

Data Freshness Timeline

(refreshed 16× in last 7d / 30× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-08-20 22:55 UTCEPSS rescore
  2. 2026-08-20 07:45 UTCVendor advisory
  3. 2026-08-20 07:45 UTCGHSA enrichment
  4. 2026-08-19 17:04 UTCEPSS rescore
  5. 2026-08-18 13:48 UTCEPSS rescore
  6. 2026-08-17 13:47 UTCEPSS rescore
  7. 2026-08-17 05:41 UTCVendor advisory
  8. 2026-08-17 05:41 UTCGHSA enrichment
  9. 2026-08-17 05:25 UTCNVD update
  10. 2026-08-17 05:13 UTCVendor advisory
  11. 2026-08-17 05:13 UTCGHSA enrichment
  12. 2026-08-17 05:05 UTCMITRE cvelistV5
  13. 2026-08-16 14:56 UTCEPSS rescore
  14. 2026-08-15 14:36 UTCVendor advisory
  15. 2026-08-15 14:36 UTCGHSA enrichment
  16. 2026-08-15 01:30 UTCEPSS rescore
  17. 2026-08-13 22:00 UTCEPSS rescore
  18. 2026-08-12 13:51 UTCEPSS rescore
  19. 2026-08-12 12:31 UTCVendor advisory
  20. 2026-08-12 12:31 UTCGHSA enrichment
  21. 2026-08-11 00:00 UTCEPSS rescore
  22. 2026-08-09 13:47 UTCEPSS rescore
  23. 2026-08-09 10:26 UTCEG score recompute
  24. 2026-08-09 10:26 UTCVendor advisory
  25. 2026-08-09 10:26 UTCGHSA enrichment
Show 5 more
  1. 2026-08-08 16:37 UTCEPSS rescore
  2. 2026-08-06 13:47 UTCEPSS rescore
  3. 2026-08-06 08:21 UTCNVD update
  4. 2026-08-06 07:25 UTCEG score recompute
  5. 2026-08-06 07:25 UTCMITRE cvelistV5first tracked

Frequently asked(4)

What is CVE-2026-64590?
CVE-2026-64590 is a publicly disclosed vulnerability published on August 6, 2026. In the Linux kernel, the following vulnerability has been resolved: dma-buf/udmabuf: skip redundant cpu sync to fix cacheline EEXIST warning When CONFIGDMAAPIDEBUGSG is enabled, importing a udmabuf into a DRM driver (e.g. amdgpu for video playback in GNOME Videos / Showtime) triggers a spurious…
When was CVE-2026-64590 disclosed?
CVE-2026-64590 was first published in the National Vulnerability Database on August 6, 2026, with the most recent update on August 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-64590 actively exploited?
CVE-2026-64590 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 94.7% of all scored CVEs.
How do I remediate CVE-2026-64590?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-64590, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-64590

Explore →

Is Your Infrastructure Affected by CVE-2026-64590?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs