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 89617 fsntfs3 validate dirty page table on log replay
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-89617

fs/ntfs3: validate dirty page table on log replayCVE-2026-89617

Answer in brief

CVE-2026-89617 records a High severity (CVSS 7.8) vulnerability in fs/ntfs3: validate dirty page table on log replay. 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 11, 2026Updated Oct 19, 2026Source checked Oct 27, 2026First seen by HOL Sep 11, 2026Material review Oct 19, 2026
Upstream Advisory

Record context

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

Key facts

Risk
High · CVSS 7.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 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). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
PackageAffected rangeFixed version
Linux/Linuxgeneric>=b46acd6a6a627d876898e1c84d3f84902264b445 <1200c2779c43b62656ccbb67df9468a7a9af2484 || >=b46acd6a6a627d876898e1c84d3f84902264b445 <2d94ffc9d7b5bb3517b129fe63b52d84bcd4ae56 || >=b46acd6a6a627d876898e1c84d3f84902264b445 <0908da07c23be4f94b99dfd9a94765525f0fe4bd || >=b46acd6a6a627d876898e1c84d3f84902264b445 <006cb7713dec10368e699abc4367e5faa334c9a51200c2779c43b62656ccbb67df9468a7a9af2484, 2d94ffc9d7b5bb3517b129fe63b52d84bcd4ae56, 0908da07c23be4f94b99dfd9a94765525f0fe4bd, 006cb7713dec10368e699abc4367e5faa334c9a5
Linux/Linuxgeneric5.15Not reported
Linux/Linuxgeneric>=b46acd6a6a627d876898e1c84d3f84902264b445 <0e07ea2fc45a7b4757ef7bf1f692cc0180a08323 || >=b46acd6a6a627d876898e1c84d3f84902264b445 <1e90b1703ee1a04cd3e9e399353fc536f5f3ba10 || >=b46acd6a6a627d876898e1c84d3f84902264b445 <d23155634a4bc1183e761d5eb2c043b2e693cc98 || >=b46acd6a6a627d876898e1c84d3f84902264b445 <1200c2779c43b62656ccbb67df9468a7a9af2484 || >=b46acd6a6a627d876898e1c84d3f84902264b445 <2d94ffc9d7b5bb3517b129fe63b52d84bcd4ae56 || >=b46acd6a6a627d876898e1c84d3f84902264b445 <0908da07c23be4f94b99dfd9a94765525f0fe4bd || >=b46acd6a6a627d876898e1c84d3f84902264b445 <006cb7713dec10368e699abc4367e5faa334c9a50e07ea2fc45a7b4757ef7bf1f692cc0180a08323, 1e90b1703ee1a04cd3e9e399353fc536f5f3ba10, d23155634a4bc1183e761d5eb2c043b2e693cc98, 1200c2779c43b62656ccbb67df9468a7a9af2484, 2d94ffc9d7b5bb3517b129fe63b52d84bcd4ae56, 0908da07c23be4f94b99dfd9a94765525f0fe4bd, 006cb7713dec10368e699abc4367e5faa334c9a5

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 1200c2779c43b62656ccbb67df9468a7a9af2484; Linux/Linux to 0e07ea2fc45a7b4757ef7bf1f692cc0180a08323 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 19, 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
  • Source referencegit.kernel.org
  • Source referencegit.kernel.org
Upstream source description

In the Linux kernel, the following vulnerability has been resolved: fs/ntfs3: validate dirty page table on log replay Each DIR_PAGE_ENTRY ends in a page_lcns[] array whose length is the on-disk lcns_follow field. check_rstbl() validates the table bookkeeping but never checks that this array fits in the entry, so a crafted lcns_follow lets the v0->v1 conversion memmove and later replay passes run off the entry. Add check_dp_table() to reject, right after check_rstbl(), any entry larger than its size claims via struct_size() (the same expression used to allocate these entries, so the check is overflow-safe by construction). All consumers can then trust lcns_follow as the real capacity. This covers every page_lcns[] access whose index is bounded by the entry itself (the conversion memmove, the HotFix store via find_dp(), and the self-bounded scan loops). Accesses whose index comes from the log record need a separate bound and are handled in a follow-up patch.

Quoted source text, attributed separately from HOL analysis.