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 64016 ksmbd fix durable reconnect error path file
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-64016

ksmbd: fix durable reconnect error path file lifetimeCVE-2026-64016

Answer in brief

CVE-2026-64016 records a Critical severity (CVSS 9.8) vulnerability in ksmbd: fix durable reconnect error path file lifetime. 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 19, 2026Updated Oct 13, 2026Source checked Nov 4, 2026First seen by HOL Aug 5, 2026Material review Oct 13, 2026
Upstream Advisory

Key facts

Risk
Critical · CVSS 9.8
Exploitation
Not marked as known exploited
Affected software
9 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.

Affected products and reported versions
ProductAffected versionsFixed versions
cpe:2.3:o:linux:linux_kernel:6.18.33:*:*:*:*:*:*:*Not reportedNot reported
cpe:2.3:o:linux:linux_kernel:7.0.10:*:*:*:*:*:*:*Not reportedNot reported
cpe:2.3:o:linux:linux_kernel:7.1:rc1:*:*:*:*:*:*Not reportedNot reported
cpe:2.3:o:linux:linux_kernel:7.1:rc2:*:*:*:*:*:*Not reportedNot reported
cpe:2.3:o:linux:linux_kernel:7.1:rc3:*:*:*:*:*:*Not reportedNot reported
cpe:2.3:o:linux:linux_kernel:7.1:rc4:*:*:*:*:*:*Not reportedNot reported
Mapped affected packages and fixed versions
PackageAffected rangeFixed version
Linux/Linuxgeneric>=ce2e164c1c51c3f7813b80f8c926836e896bcbb3 <a1a39f227c80cbf369767badc32cba2b225147d1 || >=97a0cd55283b4e63fd92804da91c8d9896adcad9 <6cb0b9385320110fe24a5d5ac0000ade4bb3a3f3 || >=1baff47b81f94f9231c91236aa511420d0e266b9 <3515503322f4819277091839eed46b695096aca5a1a39f227c80cbf369767badc32cba2b225147d1, 6cb0b9385320110fe24a5d5ac0000ade4bb3a3f3, 3515503322f4819277091839eed46b695096aca5
Linux/Linuxgeneric>=6.18.33 <6.18.34 || >=7.0.10 <7.0.116.18.34, 7.0.11
Linux/Linuxgeneric>=f0ff7f12398e85b3a11745ff7feab6246f3d75c2 <5e641e4ee0bc1937408d41051a908ad4151be63b || >=4db3dcac84c2f14a45ae201efb38de1fb1bfc009 <478bfaa036bd0c7e179acff8b8484bccdee3b8c7 || >=ce2e164c1c51c3f7813b80f8c926836e896bcbb3 <a1a39f227c80cbf369767badc32cba2b225147d1 || >=97a0cd55283b4e63fd92804da91c8d9896adcad9 <6cb0b9385320110fe24a5d5ac0000ade4bb3a3f3 || >=1baff47b81f94f9231c91236aa511420d0e266b9 <3515503322f4819277091839eed46b695096aca55e641e4ee0bc1937408d41051a908ad4151be63b, 478bfaa036bd0c7e179acff8b8484bccdee3b8c7, a1a39f227c80cbf369767badc32cba2b225147d1, 6cb0b9385320110fe24a5d5ac0000ade4bb3a3f3, 3515503322f4819277091839eed46b695096aca5

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 a1a39f227c80cbf369767badc32cba2b225147d1; Linux/Linux to 6.18.34; Linux/Linux to 5e641e4ee0bc1937408d41051a908ad4151be63b if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

  1. Published upstream

    Jul 19, 2026

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

    Oct 13, 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
Upstream source description

In the Linux kernel, the following vulnerability has been resolved: ksmbd: fix durable reconnect error path file lifetime After a durable reconnect succeeds, ksmbd_reopen_durable_fd() republishes the same ksmbd_file into the session volatile-id table. If smb2_open() then takes a later error path, cleanup first calls ksmbd_fd_put(work, fp) and then unconditionally calls ksmbd_put_durable_fd(dh_info.fp). In this case fp and dh_info.fp are the same object. The first put drops the reconnect lookup reference, but the final durable put can run __ksmbd_close_fd(NULL, fp). Because the final close is not session-aware, it can free the file object without removing the volatile-id entry that was just published into the session table. Use the session-aware put for the final reconnect drop when the reconnect had already succeeded and the error path is cleaning up the republished file. Earlier reconnect failures, before fp is assigned to dh_info.fp, keep using the durable-only put path.

Quoted source text, attributed separately from HOL analysis.

Record context

Vulnerability class
Memory Corruption
EPSS
Not reported
CWE IDs
CWE-416
Source
CVE List V5
Source checked
Nov 4, 2026
References
5 linked sources
Open source record