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 89840 f2fs validate moverange destination size
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.1CVE-2026-89840

f2fs: validate MOVE_RANGE destination sizeCVE-2026-89840

Answer in brief

CVE-2026-89840 records a High severity (CVSS 7.1) vulnerability in f2fs: validate MOVE_RANGE destination size. 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) and additional mapped packages. 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
High · CVSS 7.1
Exploitation
Not marked as known exploited
Affected software
6 mapped packages or products
Fix availability
Available

Why this deserves its current priority

CVSS is 7.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), Linux/Linux (generic) and additional mapped packages. Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
PackageAffected rangeFixed version
Linux/Linuxgeneric>=4dd6f977fc778e5a0da604e5f8cb2f36d163d27b <bca61ee5192ea47003722486ae9588a2a4bb47b6 || >=4dd6f977fc778e5a0da604e5f8cb2f36d163d27b <db13064669526494cd78ba3a4394063b740e940c || >=4dd6f977fc778e5a0da604e5f8cb2f36d163d27b <dcae1eeda53149f219dd6af93b3083b7271c1c63 || >=4dd6f977fc778e5a0da604e5f8cb2f36d163d27b <e533889fc26aea0cd83c90327063f272061dd820bca61ee5192ea47003722486ae9588a2a4bb47b6, db13064669526494cd78ba3a4394063b740e940c, dcae1eeda53149f219dd6af93b3083b7271c1c63, e533889fc26aea0cd83c90327063f272061dd820
Linux/Linuxgeneric4.8Not reported
Linux/Linuxgeneric>=4dd6f977fc778e5a0da604e5f8cb2f36d163d27b <dcae1eeda53149f219dd6af93b3083b7271c1c63 || >=4dd6f977fc778e5a0da604e5f8cb2f36d163d27b <e533889fc26aea0cd83c90327063f272061dd820dcae1eeda53149f219dd6af93b3083b7271c1c63, e533889fc26aea0cd83c90327063f272061dd820
Linux/Linuxgeneric>=4dd6f977fc778e5a0da604e5f8cb2f36d163d27b <db13064669526494cd78ba3a4394063b740e940c || >=4dd6f977fc778e5a0da604e5f8cb2f36d163d27b <dcae1eeda53149f219dd6af93b3083b7271c1c63 || >=4dd6f977fc778e5a0da604e5f8cb2f36d163d27b <e533889fc26aea0cd83c90327063f272061dd820db13064669526494cd78ba3a4394063b740e940c, dcae1eeda53149f219dd6af93b3083b7271c1c63, e533889fc26aea0cd83c90327063f272061dd820
Linux/Linuxgeneric>=4dd6f977fc778e5a0da604e5f8cb2f36d163d27b <54c587f3f95ce2d6932a16566db83f73cc4313e1 || >=4dd6f977fc778e5a0da604e5f8cb2f36d163d27b <bca61ee5192ea47003722486ae9588a2a4bb47b6 || >=4dd6f977fc778e5a0da604e5f8cb2f36d163d27b <db13064669526494cd78ba3a4394063b740e940c || >=4dd6f977fc778e5a0da604e5f8cb2f36d163d27b <dcae1eeda53149f219dd6af93b3083b7271c1c63 || >=4dd6f977fc778e5a0da604e5f8cb2f36d163d27b <e533889fc26aea0cd83c90327063f272061dd82054c587f3f95ce2d6932a16566db83f73cc4313e1, bca61ee5192ea47003722486ae9588a2a4bb47b6, db13064669526494cd78ba3a4394063b740e940c, dcae1eeda53149f219dd6af93b3083b7271c1c63, e533889fc26aea0cd83c90327063f272061dd820
Linux/Linuxgeneric>=4dd6f977fc778e5a0da604e5f8cb2f36d163d27b <454de20a5a36c000b75f49337aae8c92045c5242 || >=4dd6f977fc778e5a0da604e5f8cb2f36d163d27b <54c587f3f95ce2d6932a16566db83f73cc4313e1 || >=4dd6f977fc778e5a0da604e5f8cb2f36d163d27b <bca61ee5192ea47003722486ae9588a2a4bb47b6 || >=4dd6f977fc778e5a0da604e5f8cb2f36d163d27b <db13064669526494cd78ba3a4394063b740e940c || >=4dd6f977fc778e5a0da604e5f8cb2f36d163d27b <dcae1eeda53149f219dd6af93b3083b7271c1c63 || >=4dd6f977fc778e5a0da604e5f8cb2f36d163d27b <e533889fc26aea0cd83c90327063f272061dd820454de20a5a36c000b75f49337aae8c92045c5242, 54c587f3f95ce2d6932a16566db83f73cc4313e1, bca61ee5192ea47003722486ae9588a2a4bb47b6, db13064669526494cd78ba3a4394063b740e940c, dcae1eeda53149f219dd6af93b3083b7271c1c63, e533889fc26aea0cd83c90327063f272061dd820

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 bca61ee5192ea47003722486ae9588a2a4bb47b6; Linux/Linux to dcae1eeda53149f219dd6af93b3083b7271c1c63; Linux/Linux to db13064669526494cd78ba3a4394063b740e940c; Linux/Linux to 54c587f3f95ce2d6932a16566db83f73cc4313e1; Linux/Linux to 454de20a5a36c000b75f49337aae8c92045c5242 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
  • Source referencegit.kernel.org
Upstream source description

In the Linux kernel, the following vulnerability has been resolved: f2fs: validate MOVE_RANGE destination size F2FS_IOC_MOVE_RANGE checks the source range, but not the destination end before updating i_size. A source hole can expose this: __clone_blkaddrs() skips NULL_ADDR entries and returns success, so the caller can still extend the destination inode with unchecked pos_out + len. Reject destination overflow and use inode_newsize_ok() before extending the destination inode.

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
6 linked sources
Open source record