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 89788 ksmbd fix tree connection use after free in
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
  • Telegram
  • X
More
  • About HOL
  • Sponsor
  • Advertise
  • 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-89788

ksmbd: fix tree connection use-after-free in smb2_tree_connect()CVE-2026-89788

Answer in brief

CVE-2026-89788 records a Critical severity (CVSS 9.8) vulnerability in ksmbd: fix tree connection use-after-free in smb2_tree_connect(). The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), 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 Sep 16, 2026Updated Oct 30, 2026Source checked Oct 31, 2026First seen by HOL Sep 16, 2026Material review Oct 30, 2026
Upstream Advisory

Key facts

Risk
Critical · CVSS 9.8
Exploitation
Not marked as known exploited
Affected software
4 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), Linux/Linux (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
PackageAffected rangeFixed version
Linux/Linuxgeneric>=33b235a6e6ebe0f05f3586a71e8d281d00f71e2e <4e30fbd26e84efa2e5cbec4eb11e126ac0c79313 || >=33b235a6e6ebe0f05f3586a71e8d281d00f71e2e <b5ec6c462aab1062cf5d1e667ba7c6442f737055 || dd45db4d9bbc8f122a9b4db5ce94ae29fcf03d3c || 7b58ee8d0b91359554cf219cd4f33872ea2afd66 || >=5.15.145 <5.16 || >=6.1.71 <6.24e30fbd26e84efa2e5cbec4eb11e126ac0c79313, b5ec6c462aab1062cf5d1e667ba7c6442f737055, 5.16, 6.2
Linux/Linuxgeneric6.6Not reported
Linux/Linuxgeneric>=33b235a6e6ebe0f05f3586a71e8d281d00f71e2e <ca3a3984bf445aaec69f6937f11e560d4b849365 || >=33b235a6e6ebe0f05f3586a71e8d281d00f71e2e <bd58a52738f7576ee5f5eb74243df13f902c8051 || >=33b235a6e6ebe0f05f3586a71e8d281d00f71e2e <4e30fbd26e84efa2e5cbec4eb11e126ac0c79313 || >=33b235a6e6ebe0f05f3586a71e8d281d00f71e2e <b5ec6c462aab1062cf5d1e667ba7c6442f737055 || dd45db4d9bbc8f122a9b4db5ce94ae29fcf03d3c || 7b58ee8d0b91359554cf219cd4f33872ea2afd66 || >=5.15.145 <5.16 || >=6.1.71 <6.2ca3a3984bf445aaec69f6937f11e560d4b849365, bd58a52738f7576ee5f5eb74243df13f902c8051, 4e30fbd26e84efa2e5cbec4eb11e126ac0c79313, b5ec6c462aab1062cf5d1e667ba7c6442f737055, 5.16, 6.2
Linux/Linuxgeneric>=7b58ee8d0b91359554cf219cd4f33872ea2afd66 <63f5939b50470ef4d245c16d2098376b952beb51 || >=33b235a6e6ebe0f05f3586a71e8d281d00f71e2e <ca3a3984bf445aaec69f6937f11e560d4b849365 || >=33b235a6e6ebe0f05f3586a71e8d281d00f71e2e <bd58a52738f7576ee5f5eb74243df13f902c8051 || >=33b235a6e6ebe0f05f3586a71e8d281d00f71e2e <4e30fbd26e84efa2e5cbec4eb11e126ac0c79313 || >=33b235a6e6ebe0f05f3586a71e8d281d00f71e2e <b5ec6c462aab1062cf5d1e667ba7c6442f737055 || dd45db4d9bbc8f122a9b4db5ce94ae29fcf03d3c || >=6.1.71 <6.1.191 || >=5.15.145 <5.1663f5939b50470ef4d245c16d2098376b952beb51, ca3a3984bf445aaec69f6937f11e560d4b849365, bd58a52738f7576ee5f5eb74243df13f902c8051, 4e30fbd26e84efa2e5cbec4eb11e126ac0c79313, b5ec6c462aab1062cf5d1e667ba7c6442f737055, 6.1.191, 5.16

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 4e30fbd26e84efa2e5cbec4eb11e126ac0c79313; Linux/Linux to ca3a3984bf445aaec69f6937f11e560d4b849365; Linux/Linux to 63f5939b50470ef4d245c16d2098376b952beb51 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

  1. Published upstream

    Sep 16, 2026

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

    Oct 30, 2026

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

    Sep 16, 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 tree connection use-after-free in smb2_tree_connect() ksmbd_tree_conn_connect() publishes a new tree connection in sess->tree_conns with a single reference and returns its pointer to smb2_tree_connect(). The handler continues to initialize the object and build the response after publication. A concurrent session logoff can erase the connection and drop that reference, freeing the object while the handler still uses it. BUG: KASAN: slab-use-after-free in smb2_tree_connect+0xe3d/0xf90 smb2_tree_connect (fs/smb/server/smb2pdu.c:2872) handle_ksmbd_work process_one_work worker_thread kthread After xa_store() succeeds, take a second reference before releasing tree_conns_lock. The original reference belongs to the xarray entry and the second belongs to the creating smb2_tree_connect() handler. Keep the references balanced in every path: - On normal exit or an error after publication, smb2_tree_connect() drops its creator reference. Error cleanup also calls ksmbd_tree_conn_disconnect(), which drops the xarray reference only if it removes the exact entry. - SMB2 TREE_DISCONNECT uses the same helper to remove the entry and drop its xarray reference. The request's existing lookup reference remains owned by the request and is released by the existing cleanup. - Session LOGOFF removes each entry and drops its xarray reference. If it wins the race, later cleanup sees that the entry is gone and does not drop that reference again. To enforce this ownership, claim the disconnected state and erase the exact entry atomically under tree_conns_lock. This guarantees one drop for the xarray reference and one drop by each in-flight user, regardless of which teardown path wins. If logoff removes the entry before initialization completes, fail the connect instead of marking the detached object TREE_CONNECTED.

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
Oct 31, 2026
References
5 linked sources
Open source record