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 64535 nvmet tcp fix potential uaf when ddgst mismatch
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
Critical · CVSS 9.8CVE-2026-64535

nvmet-tcp: Fix potential UAF when ddgst mismatchCVE-2026-64535

Answer in brief

CVE-2026-64535 records a Critical severity (CVSS 9.8) vulnerability in nvmet-tcp: Fix potential UAF when ddgst mismatch. 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 Jul 27, 2026Updated Nov 3, 2026Source checked Nov 4, 2026First seen by HOL Aug 5, 2026Material review Nov 3, 2026
Upstream Advisory

Record context

Vulnerability class
Vulnerability
EPSS
Not reported
CWE IDs
CWE-415
Source
CVE List V5
Source checked
Nov 4, 2026
References
7 linked sources
Open source record

Key facts

Risk
Critical · CVSS 9.8
Exploitation
Not marked as known exploited
Affected software
3 mapped packages or products
Fix availability
Available

Why this deserves its current priority

CVSS is 9.8. 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>=fda871c0ba5d2eed2cd1c881573168129da70058 <96fe2513df590e74b04253a45089cae75569570e || >=fda871c0ba5d2eed2cd1c881573168129da70058 <e091ff83d962f9ed00d9bd70443676de9fe98bdc || >=fda871c0ba5d2eed2cd1c881573168129da70058 <6f9442983a3e4227afd1c83a5251ddbca585ea21 || >=fda871c0ba5d2eed2cd1c881573168129da70058 <088ee46c18d99baef453afd74181dd40ade044ad || >=fda871c0ba5d2eed2cd1c881573168129da70058 <dbbd07d0a7020b80f6a7028e561908f7b83b3d5a || 91edfca6f8b364d60cde3ddefaf7d03ddf35774b || 4b17476d809273617d3317fa0d4ae78aa488d760 || >=5.10.20 <5.11 || >=5.11.3 <5.1296fe2513df590e74b04253a45089cae75569570e, e091ff83d962f9ed00d9bd70443676de9fe98bdc, 6f9442983a3e4227afd1c83a5251ddbca585ea21, 088ee46c18d99baef453afd74181dd40ade044ad, dbbd07d0a7020b80f6a7028e561908f7b83b3d5a, 5.11, 5.12
Linux/Linuxgeneric5.12Not reported
Linux/Linuxgeneric>=91edfca6f8b364d60cde3ddefaf7d03ddf35774b <dfb902462bca478f050224ec7a7195aafa7643b1 || >=fda871c0ba5d2eed2cd1c881573168129da70058 <7e558308eba14c8136cb1e615f0c850f76d1fc0a || >=fda871c0ba5d2eed2cd1c881573168129da70058 <96fe2513df590e74b04253a45089cae75569570e || >=fda871c0ba5d2eed2cd1c881573168129da70058 <e091ff83d962f9ed00d9bd70443676de9fe98bdc || >=fda871c0ba5d2eed2cd1c881573168129da70058 <6f9442983a3e4227afd1c83a5251ddbca585ea21 || >=fda871c0ba5d2eed2cd1c881573168129da70058 <088ee46c18d99baef453afd74181dd40ade044ad || >=fda871c0ba5d2eed2cd1c881573168129da70058 <dbbd07d0a7020b80f6a7028e561908f7b83b3d5a || 4b17476d809273617d3317fa0d4ae78aa488d760 || >=5.10.20 <5.10.265 || >=5.11.3 <5.12dfb902462bca478f050224ec7a7195aafa7643b1, 7e558308eba14c8136cb1e615f0c850f76d1fc0a, 96fe2513df590e74b04253a45089cae75569570e, e091ff83d962f9ed00d9bd70443676de9fe98bdc, 6f9442983a3e4227afd1c83a5251ddbca585ea21, 088ee46c18d99baef453afd74181dd40ade044ad, dbbd07d0a7020b80f6a7028e561908f7b83b3d5a, 5.10.265, 5.12

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 96fe2513df590e74b04253a45089cae75569570e; Linux/Linux to dfb902462bca478f050224ec7a7195aafa7643b1 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

  1. Published upstream

    Jul 27, 2026

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

    Nov 3, 2026

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

    Aug 5, 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
Upstream source description

In the Linux kernel, the following vulnerability has been resolved: nvmet-tcp: Fix potential UAF when ddgst mismatch Shivam Kumar found via vulnerability testing: When data digest is enabled on an NVMe/TCP connection and a digest mismatch occurs on a non-final H2C_DATA PDU during an R2T-based data transfer, the digest error handler in nvmet_tcp_try_recv_ddgst() calls nvmet_req_uninit() — which performs percpu_ref_put() on the submission queue — but does NOT mark the command as completed. It does not set cqe->status, does not modify rbytes_done, and does not clear any flag. When the subsequent fatal error triggers queue teardown, nvmet_tcp_uninit_data_in_cmds() iterates all commands, checks nvmet_tcp_need_data_in() for each one, and finds that the already-uninited command still appears to need data (because rbytes_done < transfer_len and cqe->status == 0). It therefore calls nvmet_req_uninit() a second time on the same command — a double percpu_ref_put against a single percpu_ref_get.

Quoted source text, attributed separately from HOL analysis.