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 90153 ksmbd bound smbcheckpermdacl ace walks by dacl
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
  • Affiliate program
  • Contact
  • Blog
  • GitHub
  • Privacy
  • Terms of Service
Settings

Copyright © 2026 HOL DAO LLC. All rights reserved.

Back to active CVEs
High · CVSS 8.1CVE-2026-90153

ksmbd: bound smb_check_perm_dacl() ACE walks by DACL sizeCVE-2026-90153

Answer in brief

CVE-2026-90153 records a High severity (CVSS 8.1) vulnerability in ksmbd: bound smb_check_perm_dacl() ACE walks by DACL size. 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 Sep 17, 2026Updated Oct 30, 2026Source checked Nov 1, 2026First seen by HOL Sep 17, 2026Material review Oct 30, 2026
Upstream Advisory

Key facts

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

Why this deserves its current priority

CVSS is 8.1. 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>=8f0541186e9ad1b62accc9519cc2b7a7240272a7 <a2051ffe452afad52f580b85a3fd8851933b1e7c || >=8f0541186e9ad1b62accc9519cc2b7a7240272a7 <a29f57a14c939586d84d7fd6a029bd1fd170098f || >=8f0541186e9ad1b62accc9519cc2b7a7240272a7 <a4a307d149327dad5fb25187e1b03cebd1b04de6 || >=8f0541186e9ad1b62accc9519cc2b7a7240272a7 <8e4f75e979c1d9a51b0a48ac33d0cfd5f039ec67 || >=8f0541186e9ad1b62accc9519cc2b7a7240272a7 <79decd88dd3f0d42e7fb0689b1a7853bfa302459 || cb69d4d6f709f87c94afa28ae64c501576692171 || 6e8f4abf584253cbaa596ea4ad13110cf61cd4c9 || 8e33102309bd6839b2e2e158f93a7b378cb4655d || >=5.15.62 <5.16 || >=5.18.18 <5.19 || >=5.19.2 <5.20a2051ffe452afad52f580b85a3fd8851933b1e7c, a29f57a14c939586d84d7fd6a029bd1fd170098f, a4a307d149327dad5fb25187e1b03cebd1b04de6, 8e4f75e979c1d9a51b0a48ac33d0cfd5f039ec67, 79decd88dd3f0d42e7fb0689b1a7853bfa302459, 5.16, 5.19, 5.20
Linux/Linuxgeneric6.0Not reported
Linux/Linuxgeneric>=8f0541186e9ad1b62accc9519cc2b7a7240272a7 <930dcdd888eabf166589e020dcbf6d15b5e13305 || >=8f0541186e9ad1b62accc9519cc2b7a7240272a7 <a2051ffe452afad52f580b85a3fd8851933b1e7c || >=8f0541186e9ad1b62accc9519cc2b7a7240272a7 <a29f57a14c939586d84d7fd6a029bd1fd170098f || >=8f0541186e9ad1b62accc9519cc2b7a7240272a7 <a4a307d149327dad5fb25187e1b03cebd1b04de6 || >=8f0541186e9ad1b62accc9519cc2b7a7240272a7 <8e4f75e979c1d9a51b0a48ac33d0cfd5f039ec67 || >=8f0541186e9ad1b62accc9519cc2b7a7240272a7 <79decd88dd3f0d42e7fb0689b1a7853bfa302459 || cb69d4d6f709f87c94afa28ae64c501576692171 || 6e8f4abf584253cbaa596ea4ad13110cf61cd4c9 || 8e33102309bd6839b2e2e158f93a7b378cb4655d || >=5.15.62 <5.16 || >=5.18.18 <5.19 || >=5.19.2 <5.20930dcdd888eabf166589e020dcbf6d15b5e13305, a2051ffe452afad52f580b85a3fd8851933b1e7c, a29f57a14c939586d84d7fd6a029bd1fd170098f, a4a307d149327dad5fb25187e1b03cebd1b04de6, 8e4f75e979c1d9a51b0a48ac33d0cfd5f039ec67, 79decd88dd3f0d42e7fb0689b1a7853bfa302459, 5.16, 5.19, 5.20

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

Evidence timeline and material changes

  1. Published upstream

    Sep 17, 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 17, 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
Upstream source description

In the Linux kernel, the following vulnerability has been resolved: ksmbd: bound smb_check_perm_dacl() ACE walks by DACL size smb_check_perm_dacl() validates that the DACL fits inside the NT security descriptor, but then bounds its two ACE walks by the remaining NTSD length (acl_size) rather than the DACL's declared size (pdacl_size). When pdacl->size is smaller than the trailing NTSD buffer, bytes after the declared DACL boundary - still inside the stored security descriptor - are parsed as ACEs during access checks. A crafted DACL can place an access-granting ACE beyond pdacl->size, and the current code accepts it during SMB2_CREATE access validation, while parse_dacl() and smb_inherit_dacl() stop at pdacl_size. Bound both ACE walks by pdacl_size to match the DACL boundary semantics used elsewhere in the server. Validation: - semantic KUnit harness shows the post-boundary ACE is selected before the fix and rejected (EACCES) after it - linux master (7.2-rc6), x86_64

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 1, 2026
References
6 linked sources
Open source record