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 90037 nfsd prevent client use after free during
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
Critical · CVSS 9.8CVE-2026-90037

NFSD: Prevent client use-after-free during close_lru reapingCVE-2026-90037

Answer in brief

CVE-2026-90037 records a Critical severity (CVSS 9.8) vulnerability in NFSD: Prevent client use-after-free during close_lru reaping. 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

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

Key facts

Risk
Critical · CVSS 9.8
Exploitation
Not marked as known exploited
Affected software
5 mapped packages or products
Fix availability
Available

Why this deserves its current priority

CVSS is 9.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) and additional mapped packages. Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
PackageAffected rangeFixed version
Linux/Linuxgeneric3.17Not reported
Linux/Linuxgeneric>=217526e7ecc9f6f243e976772e81eab7ab986a4c <0763482227822f7343557f086afc382086d56c4c || >=217526e7ecc9f6f243e976772e81eab7ab986a4c <83dd59ac1c3455c2c7d8ddb582d980a13199b9b3 || >=217526e7ecc9f6f243e976772e81eab7ab986a4c <e57a9ed34ea8c17e831de59b8f1a6b2d80d347a1 || >=217526e7ecc9f6f243e976772e81eab7ab986a4c <2330b788d732f43668b965b3105b37ceb276dfea0763482227822f7343557f086afc382086d56c4c, 83dd59ac1c3455c2c7d8ddb582d980a13199b9b3, e57a9ed34ea8c17e831de59b8f1a6b2d80d347a1, 2330b788d732f43668b965b3105b37ceb276dfea
Linux/Linuxgeneric>=217526e7ecc9f6f243e976772e81eab7ab986a4c <83dd59ac1c3455c2c7d8ddb582d980a13199b9b3 || >=217526e7ecc9f6f243e976772e81eab7ab986a4c <e57a9ed34ea8c17e831de59b8f1a6b2d80d347a1 || >=217526e7ecc9f6f243e976772e81eab7ab986a4c <2330b788d732f43668b965b3105b37ceb276dfea83dd59ac1c3455c2c7d8ddb582d980a13199b9b3, e57a9ed34ea8c17e831de59b8f1a6b2d80d347a1, 2330b788d732f43668b965b3105b37ceb276dfea
Linux/Linuxgeneric>=217526e7ecc9f6f243e976772e81eab7ab986a4c <adc34b5df5c5d87043cb500b0867fc1c4ad0117e || >=217526e7ecc9f6f243e976772e81eab7ab986a4c <0763482227822f7343557f086afc382086d56c4c || >=217526e7ecc9f6f243e976772e81eab7ab986a4c <83dd59ac1c3455c2c7d8ddb582d980a13199b9b3 || >=217526e7ecc9f6f243e976772e81eab7ab986a4c <e57a9ed34ea8c17e831de59b8f1a6b2d80d347a1 || >=217526e7ecc9f6f243e976772e81eab7ab986a4c <2330b788d732f43668b965b3105b37ceb276dfeaadc34b5df5c5d87043cb500b0867fc1c4ad0117e, 0763482227822f7343557f086afc382086d56c4c, 83dd59ac1c3455c2c7d8ddb582d980a13199b9b3, e57a9ed34ea8c17e831de59b8f1a6b2d80d347a1, 2330b788d732f43668b965b3105b37ceb276dfea
Linux/Linuxgeneric>=217526e7ecc9f6f243e976772e81eab7ab986a4c <1d721729762a413015864b2a56d7fb86fb8efa9f || >=217526e7ecc9f6f243e976772e81eab7ab986a4c <adc34b5df5c5d87043cb500b0867fc1c4ad0117e || >=217526e7ecc9f6f243e976772e81eab7ab986a4c <0763482227822f7343557f086afc382086d56c4c || >=217526e7ecc9f6f243e976772e81eab7ab986a4c <83dd59ac1c3455c2c7d8ddb582d980a13199b9b3 || >=217526e7ecc9f6f243e976772e81eab7ab986a4c <e57a9ed34ea8c17e831de59b8f1a6b2d80d347a1 || >=217526e7ecc9f6f243e976772e81eab7ab986a4c <2330b788d732f43668b965b3105b37ceb276dfea1d721729762a413015864b2a56d7fb86fb8efa9f, adc34b5df5c5d87043cb500b0867fc1c4ad0117e, 0763482227822f7343557f086afc382086d56c4c, 83dd59ac1c3455c2c7d8ddb582d980a13199b9b3, e57a9ed34ea8c17e831de59b8f1a6b2d80d347a1, 2330b788d732f43668b965b3105b37ceb276dfea

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 0763482227822f7343557f086afc382086d56c4c; Linux/Linux to 83dd59ac1c3455c2c7d8ddb582d980a13199b9b3; Linux/Linux to adc34b5df5c5d87043cb500b0867fc1c4ad0117e; Linux/Linux to 1d721729762a413015864b2a56d7fb86fb8efa9f 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: NFSD: Prevent client use-after-free during close_lru reaping An nfs4_openowner left on nn->close_lru after its final CLOSE keeps its last closed stateid in oo_last_closed_stid, holding only a raw pointer to its nfs4_client. The laundromat reaps timed-out entries, drops nn->client_lock, and calls nfs4_put_stid(), which dereferences the client through cl_lock. Nothing pins the client across that window, so a concurrent force_expire_client() can free it and nfs4_put_stid() reads freed memory. __destroy_client() hits the same race, walking clp->cl_openowners without cl_lock. Pin the client with cl_rpc_users before dropping client_lock, and skip clients already expiring. __destroy_client() then cleans up its own close_lru entries through release_last_closed_stateid(), so teardown no longer races the laundromat.

Quoted source text, attributed separately from HOL analysis.