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 89638 smb client clear setuidsetgid bit on write with
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
High · CVSS 7.8CVE-2026-89638

smb: client: clear setuid/setgid bit on write with cifsacl/modefromsid/posix extensionsCVE-2026-89638

Answer in brief

CVE-2026-89638 records a High severity (CVSS 7.8) vulnerability in smb: client: clear setuid/setgid bit on write with cifsacl/modefromsid/posix extensions. 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 11, 2026Updated Oct 21, 2026Source checked Oct 27, 2026First seen by HOL Sep 11, 2026Material review Oct 21, 2026
Upstream Advisory

Record context

Vulnerability class
Privilege Escalation
EPSS
Not reported
CWE IDs
Not reported
Source
CVE List V5
Source checked
Oct 27, 2026
References
5 linked sources
Open source record

Key facts

Risk
High · CVSS 7.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 7.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>=d32c4f2626acc385d5187bd5c0c24f442328dc60 <b10015807e4c628095d1d1d1c9307efc8cdd9e1b || >=d32c4f2626acc385d5187bd5c0c24f442328dc60 <69bfe810ecd1e0387d8975d711cd326341d13c6e || >=d32c4f2626acc385d5187bd5c0c24f442328dc60 <b8e5dc4f95e5484159b343903f302eb6d783f2e6b10015807e4c628095d1d1d1c9307efc8cdd9e1b, 69bfe810ecd1e0387d8975d711cd326341d13c6e, b8e5dc4f95e5484159b343903f302eb6d783f2e6
Linux/Linuxgeneric2.6.24Not reported
Linux/Linuxgeneric>=d32c4f2626acc385d5187bd5c0c24f442328dc60 <58b23fc9fb580432470d6c5da3c1e5660dba9fbc || >=d32c4f2626acc385d5187bd5c0c24f442328dc60 <b10015807e4c628095d1d1d1c9307efc8cdd9e1b || >=d32c4f2626acc385d5187bd5c0c24f442328dc60 <69bfe810ecd1e0387d8975d711cd326341d13c6e || >=d32c4f2626acc385d5187bd5c0c24f442328dc60 <b8e5dc4f95e5484159b343903f302eb6d783f2e658b23fc9fb580432470d6c5da3c1e5660dba9fbc, b10015807e4c628095d1d1d1c9307efc8cdd9e1b, 69bfe810ecd1e0387d8975d711cd326341d13c6e, b8e5dc4f95e5484159b343903f302eb6d783f2e6
Linux/Linuxgeneric>=d32c4f2626acc385d5187bd5c0c24f442328dc60 <7ceb6f7cb8f8f2b094e0dcdaf75757775d231378 || >=d32c4f2626acc385d5187bd5c0c24f442328dc60 <58b23fc9fb580432470d6c5da3c1e5660dba9fbc || >=d32c4f2626acc385d5187bd5c0c24f442328dc60 <b10015807e4c628095d1d1d1c9307efc8cdd9e1b || >=d32c4f2626acc385d5187bd5c0c24f442328dc60 <69bfe810ecd1e0387d8975d711cd326341d13c6e || >=d32c4f2626acc385d5187bd5c0c24f442328dc60 <b8e5dc4f95e5484159b343903f302eb6d783f2e67ceb6f7cb8f8f2b094e0dcdaf75757775d231378, 58b23fc9fb580432470d6c5da3c1e5660dba9fbc, b10015807e4c628095d1d1d1c9307efc8cdd9e1b, 69bfe810ecd1e0387d8975d711cd326341d13c6e, b8e5dc4f95e5484159b343903f302eb6d783f2e6

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 b10015807e4c628095d1d1d1c9307efc8cdd9e1b; Linux/Linux to 58b23fc9fb580432470d6c5da3c1e5660dba9fbc; Linux/Linux to 7ceb6f7cb8f8f2b094e0dcdaf75757775d231378 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

  1. Published upstream

    Sep 11, 2026

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

    Oct 21, 2026

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

    Sep 11, 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: smb: client: clear setuid/setgid bit on write with cifsacl/modefromsid/posix extensions When a file has the setuid or setgid bit set and is written to, the VFS strips those bits and issues a setattr with ATTR_KILL_SUID/ATTR_KILL_SGID together with an ATTR_MODE carrying the already-cleared mode. Both cifs_setattr_unix() and cifs_setattr_nounix() unconditionally dropped ATTR_MODE in that case: /* skip mode change if it's just for clearing setuid/setgid */ if (attrs->ia_valid & (ATTR_KILL_SUID|ATTR_KILL_SGID)) attrs->ia_valid &= ~ATTR_MODE; This is fine for the default mount, where the mode is only emulated via the DOS read-only attribute and cannot represent the setuid/setgid bits anyway. However, with the "cifsacl" or "modefromsid" mount options the mode is stored on the server through an ACL (id_mode_to_cifs_acl()), with the SMB3.1.1 POSIX extensions the mode is sent to the server directly, and with the SMB1 Unix extensions (cifs_setattr_unix) the mode is sent via CIFSSMBUnixSetPathInfo(). In all those cases dropping ATTR_MODE means the cleared mode is never pushed to the server, so the setuid/setgid bit survives the write. This is a security issue: on local filesystems the setuid bit is stripped when a file is written, but over these cifs.ko mounts the bit persists on the server, potentially allowing an unexpected privilege escalation on subsequent execution. Fix this in two places: 1. cifs_setattr_nounix(): only take the "skip mode change" shortcut when the mode is emulated via the DOS read-only attribute (i.e. neither cifsacl/modefromsid nor the SMB3.1.1 POSIX extensions are in effect), so that the cleared mode is propagated to the server in the ACL / POSIX cases. 2. cifs_setattr_unix(): this function is only called when Unix extensions are in effect, so the mode is always stored on the server. Remove the shortcut entirely so that the cleared mode is always pushed.

Quoted source text, attributed separately from HOL analysis.