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 90204 ocfs2 validate dio orphan slot during inode read
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 7.8CVE-2026-90204

ocfs2: validate DIO orphan slot during inode readCVE-2026-90204

Answer in brief

CVE-2026-90204 records a High severity (CVSS 7.8) vulnerability in ocfs2: validate DIO orphan slot during inode read. 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 17, 2026Updated Oct 30, 2026Source checked Nov 1, 2026First seen by HOL Sep 17, 2026Material review Oct 30, 2026
Upstream Advisory

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

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>=06ee5c75b57564435933fc0ffa72dc18a2fda0e7 <e35fa6eb4d2a39f8049f62361a4b44930882b5f8 || >=06ee5c75b57564435933fc0ffa72dc18a2fda0e7 <418e0ae42fa769d354b15e62c01a00413024755b || >=06ee5c75b57564435933fc0ffa72dc18a2fda0e7 <bb88131c9831075b8dc08cdd375743e5d44c7ca2e35fa6eb4d2a39f8049f62361a4b44930882b5f8, 418e0ae42fa769d354b15e62c01a00413024755b, bb88131c9831075b8dc08cdd375743e5d44c7ca2
Linux/Linuxgeneric4.0Not reported
Linux/Linuxgeneric>=06ee5c75b57564435933fc0ffa72dc18a2fda0e7 <eacdd27ca829747d4372fbae8617151072a4d1e5 || >=06ee5c75b57564435933fc0ffa72dc18a2fda0e7 <8f7a2c5cf23d437acab7f3e739bfcad0f443c554 || >=06ee5c75b57564435933fc0ffa72dc18a2fda0e7 <e35fa6eb4d2a39f8049f62361a4b44930882b5f8 || >=06ee5c75b57564435933fc0ffa72dc18a2fda0e7 <418e0ae42fa769d354b15e62c01a00413024755b || >=06ee5c75b57564435933fc0ffa72dc18a2fda0e7 <bb88131c9831075b8dc08cdd375743e5d44c7ca2eacdd27ca829747d4372fbae8617151072a4d1e5, 8f7a2c5cf23d437acab7f3e739bfcad0f443c554, e35fa6eb4d2a39f8049f62361a4b44930882b5f8, 418e0ae42fa769d354b15e62c01a00413024755b, bb88131c9831075b8dc08cdd375743e5d44c7ca2
Linux/Linuxgeneric>=06ee5c75b57564435933fc0ffa72dc18a2fda0e7 <b5fcd0aa818e08ede9a1d705ffadb0a19b565ebc || >=06ee5c75b57564435933fc0ffa72dc18a2fda0e7 <eacdd27ca829747d4372fbae8617151072a4d1e5 || >=06ee5c75b57564435933fc0ffa72dc18a2fda0e7 <8f7a2c5cf23d437acab7f3e739bfcad0f443c554 || >=06ee5c75b57564435933fc0ffa72dc18a2fda0e7 <e35fa6eb4d2a39f8049f62361a4b44930882b5f8 || >=06ee5c75b57564435933fc0ffa72dc18a2fda0e7 <418e0ae42fa769d354b15e62c01a00413024755b || >=06ee5c75b57564435933fc0ffa72dc18a2fda0e7 <bb88131c9831075b8dc08cdd375743e5d44c7ca2b5fcd0aa818e08ede9a1d705ffadb0a19b565ebc, eacdd27ca829747d4372fbae8617151072a4d1e5, 8f7a2c5cf23d437acab7f3e739bfcad0f443c554, e35fa6eb4d2a39f8049f62361a4b44930882b5f8, 418e0ae42fa769d354b15e62c01a00413024755b, bb88131c9831075b8dc08cdd375743e5d44c7ca2

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 e35fa6eb4d2a39f8049f62361a4b44930882b5f8; Linux/Linux to eacdd27ca829747d4372fbae8617151072a4d1e5; Linux/Linux to b5fcd0aa818e08ede9a1d705ffadb0a19b565ebc 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: ocfs2: validate DIO orphan slot during inode read [BUG] A corrupted append-DIO dinode (high byte at offset 0xa1 corrupted from 0 to 1) can carry an i_dio_orphaned_slot outside the mounted filesystem slot range and trigger a use-after-free error: BUG: KASAN: slab-use-after-free in ocfs2_get_system_file_inode+0x780/0x820 fs/ocfs2/sysfile.c:102 Read of size 8 at addr ffff88800b767c00 by task kworker/u8:3/85 Call Trace: ... ocfs2_get_system_file_inode+0x780/0x820 fs/ocfs2/sysfile.c:102 ocfs2_wipe_inode+0x292/0xf70 fs/ocfs2/inode.c:840 ocfs2_delete_inode fs/ocfs2/inode.c:1155 [inline] ocfs2_evict_inode+0x6c9/0x1170 fs/ocfs2/inode.c:1295 evict+0x38e/0x8f0 fs/inode.c:810 iput_final fs/inode.c:1914 [inline] iput fs/inode.c:1966 [inline] iput+0x55b/0x8b0 fs/inode.c:1926 ocfs2_recover_orphans+0x610/0xe40 fs/ocfs2/journal.c:2374 ocfs2_complete_recovery+0x5af/0xd00 fs/ocfs2/journal.c:1373 ... [CAUSE] ocfs2_del_inode_from_orphan() uses i_dio_orphaned_slot to index the slot-local system inode cache. The dinode validator does not check this active slot, so an out-of-range value produces an invalid cache entry pointer that is dereferenced as an inode pointer. [FIX] Reject an active i_dio_orphaned_slot outside the slot range during dinode validation, before DIO orphan recovery can consume it.

Quoted source text, attributed separately from HOL analysis.