HOL LogoGuard

Explore HOL

  • HOL home
  • AI agent registry
  • AI plugins
  • Open standards
  • HOL members
  • Sponsor HOL
  • Advertise with HOL

Guard product

  • Guard overviewLocal security and control for AI agents and the tools they use.
  • FeaturesRuntime protection, policy routing, review, and evidence.

Explore Guard

  • Product previewWalk through Guard surfaces in read-only demo mode.
  • ComparisonCompare Guard with native controls and AI security vendors.

AI tools

  • All AI toolsEvery supported AI tool and how Guard applies policy to it.
  • Codex
  • Claude Code
  • Cursor
  • Antigravity CLI
  • OpenCode
  • Hermes
  • OpenClaw
  • GitHub Copilot CLI
  • Antigravity
  • Kimi
  • Grok
  • Pi / Oh My Pi
  • Zcode

Extensions

  • All extensionsBrowse command and MCP coverage with owners and stated limits.
  • Command coverageShell command protection across clouds, databases, backups, and packages.
  • MCP server coverageSee how Guard maps risk state across MCP tools and servers.
  • Core safetyThe safety floor listings that ship with Guard.
  • Data and resilienceBackup and storage command protection.
  • Cloud and infrastructureAWS, Azure, GCP, Kubernetes, and more.

Security

  • AI security hubSecurity research, advisories, and agent safety coverage.
  • AI tool securitySecurity profiles for each supported coding agent.
  • Safe labsHands-on attack simulations with safe boundaries.
  • Redacted warningsReal blocked actions with sensitive details removed.
  • AdvisoriesCoordinated disclosure reports for AI tooling.
  • Active CVEsSearch active CVEs affecting AI tooling.

Learn

  • Security guidesPractical guides for securing AI agent workflows.
  • DocsInstall, configure, and operate Guard with confidence.
  • ResearchPublished security research, benchmarks, and methodology.

Community

  • ReleasesVersion history, shipped changes and upgrade notes.
  • ContributorsThe people and contributions behind HOL Guard.
  • AffiliatesShare Guard with your audience and earn from referrals.
  • SponsorFund agreed research, implementation and shared testing through the HOL Partner Program.
  • AdvertiseCompare README logo placements, previews and monthly prices, or promote a plugin or extension.
PricingEnterpriseOpen AppInstall Guard
  1. Guard
  2. Security
  3. CVEs
  4. CVE 2026 64590 dma bufudmabuf skip redundant cpu sync to fix
HOL Guard

Public security guidance for teams protecting AI harnesses, MCP servers, skills, prompts, and local tool execution.

Install Guard

AI Security

  • Prompt injection
  • MCP security
  • OWASP MCP mapping
  • Supply chain

Resources

  • Trust packet
  • Harness setup
  • Redacted warnings
  • Safe labs

Product

  • Install Guard
  • Pricing
  • Open dashboard
Guard
  • Guard Overview
  • Releases
  • Contributors
  • Install Guard
  • Pricing
Docs
  • Documentation Index
  • Developer Hub
  • API Reference
  • Root OpenAPI
  • Registry OpenAPI
  • Run in Postman
  • Standards
  • Submit ERC-8004 Contract
  • Feature Your Agent
Best Plugins
  • Browse Plugins
  • Plugin Launches
  • Best Claude Plugins
  • Best Codex Plugins
  • Best Grok Plugins
  • Best Kimi Plugins
  • Best DeepSeek Plugins
  • Best Antigravity Plugins
  • Best MCP Servers
  • Best Cursor Plugins
  • Best OpenCode Plugins
Best Agents
  • Best ERC-8004 Agents
  • Best Virtuals Agents
  • Best MCP Servers
  • Best A2A Agents
  • Best x402 Payable
  • All Categories
Community
  • Contribute to HOL
  • Telegram
  • X
More
  • About HOL
  • Sponsor
  • Advertise
  • Affiliate program
  • Contact
  • Blog
  • GitHub
  • Privacy
  • Terms of Service
Settings

Copyright © 2026 HOL DAO LLC. All rights reserved.

Back to active CVEs
Unknown severity · Source severity not reportedCVE-2026-64590

dma-buf/udmabuf: skip redundant cpu sync to fix cacheline EEXIST warningCVE-2026-64590

Answer in brief

CVE-2026-64590 records a Unknown severity vulnerability in dma-buf/udmabuf: skip redundant cpu sync to fix cacheline EEXIST warning. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), 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.

Published Aug 6, 2026Updated Aug 23, 2026Source checked Nov 5, 2026First seen by HOL Aug 6, 2026Material review Aug 23, 2026
Upstream Advisory

Key facts

Risk
Unknown severitySource severity not reported
Exploitation
Not marked as known exploited
Affected software
3 mapped packages or products
Fix availability
Available

Why this deserves its current priority

A CVSS score is not reported in the current record. 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.

Affected scope and exposure questions

The current feed maps Linux/Linux (generic), Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
PackageAffected rangeFixed version
Linux/Linuxgeneric>=284562e1f34874e267d4f499362c3816f8f6bc3f <0db56e7eae932f8e2f3eb44ad1a63633d8f504f8 || >=284562e1f34874e267d4f499362c3816f8f6bc3f <d6552f5cff795d60e629f37513ecf23d88fd2f82 || >=284562e1f34874e267d4f499362c3816f8f6bc3f <34696563461c9a23177feb6d8aff43f4c0510278 || >=284562e1f34874e267d4f499362c3816f8f6bc3f <0449a6583c0ee76778d314e4e82f166fc97fa9d8 || >=284562e1f34874e267d4f499362c3816f8f6bc3f <504e2b4ab97a51d56d966cd36d0997ad30b65b2d0db56e7eae932f8e2f3eb44ad1a63633d8f504f8, d6552f5cff795d60e629f37513ecf23d88fd2f82, 34696563461c9a23177feb6d8aff43f4c0510278, 0449a6583c0ee76778d314e4e82f166fc97fa9d8, 504e2b4ab97a51d56d966cd36d0997ad30b65b2d
Linux/Linuxgeneric5.6Not reported
Linux/Linuxgeneric>=284562e1f34874e267d4f499362c3816f8f6bc3f <4a7c644e632741c2a3116a0d3da6c11de957a6ba || >=284562e1f34874e267d4f499362c3816f8f6bc3f <01126abc11bcc6a45b664293b0b5df715be911d7 || >=284562e1f34874e267d4f499362c3816f8f6bc3f <dd7f1e572f44d3d039dc77e3989f537196c3bf52 || >=284562e1f34874e267d4f499362c3816f8f6bc3f <0db56e7eae932f8e2f3eb44ad1a63633d8f504f8 || >=284562e1f34874e267d4f499362c3816f8f6bc3f <d6552f5cff795d60e629f37513ecf23d88fd2f82 || >=284562e1f34874e267d4f499362c3816f8f6bc3f <34696563461c9a23177feb6d8aff43f4c0510278 || >=284562e1f34874e267d4f499362c3816f8f6bc3f <0449a6583c0ee76778d314e4e82f166fc97fa9d8 || >=284562e1f34874e267d4f499362c3816f8f6bc3f <504e2b4ab97a51d56d966cd36d0997ad30b65b2d4a7c644e632741c2a3116a0d3da6c11de957a6ba, 01126abc11bcc6a45b664293b0b5df715be911d7, dd7f1e572f44d3d039dc77e3989f537196c3bf52, 0db56e7eae932f8e2f3eb44ad1a63633d8f504f8, d6552f5cff795d60e629f37513ecf23d88fd2f82, 34696563461c9a23177feb6d8aff43f4c0510278, 0449a6583c0ee76778d314e4e82f166fc97fa9d8, 504e2b4ab97a51d56d966cd36d0997ad30b65b2d

Recommended response

  1. 1Check inventory. Check lockfiles and deployed manifests for Linux/Linux, Linux/Linux, Linux/Linux.
  2. 2Review the reported fix. Update Linux/Linux to 0db56e7eae932f8e2f3eb44ad1a63633d8f504f8; Linux/Linux to 4a7c644e632741c2a3116a0d3da6c11de957a6ba if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

  1. Published upstream

    Aug 6, 2026

    Evidence: source:cvelist:source_dates:source-dates:record
  2. Source modified

    Aug 23, 2026

    Evidence: source:cvelist:source_dates:source-dates:record
  3. First seen by HOL

    Aug 6, 2026

Sources and claim methodology

  • Source referencegit.kernel.org
  • Source referencegit.kernel.org
  • Source referencegit.kernel.org
  • Source referencegit.kernel.org
  • Source referencegit.kernel.org
  • Source referencegit.kernel.org
  • Source referencegit.kernel.org
  • Source referencegit.kernel.org
Upstream source description

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.

Quoted source text, attributed separately from HOL analysis.

Record context

Vulnerability class
Vulnerability
EPSS
Not reported
CWE IDs
Not reported
Source
CVE List V5
Source checked
Nov 5, 2026
References
8 linked sources
Open source record