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 90149 nfsv4flexfiles fix null dereference for nfsv40
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.5CVE-2026-90149

NFSv4/flexfiles: fix NULL dereference for NFSv4.0 data serversCVE-2026-90149

Answer in brief

CVE-2026-90149 records a High severity (CVSS 7.5) vulnerability in NFSv4/flexfiles: fix NULL dereference for NFSv4.0 data servers. 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.5
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.5. 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>=a7878ca140084ec267ede48fce64d7e60f6d873e <163c16e01f53fc8eb8d0f3484ae6c382265ecbbd || >=a7878ca140084ec267ede48fce64d7e60f6d873e <436a214514e24103159aea455147d58b44a8a585 || >=a7878ca140084ec267ede48fce64d7e60f6d873e <2b03ebbf8d5e8f6af4ecd6c65375232dd1ec32cc163c16e01f53fc8eb8d0f3484ae6c382265ecbbd, 436a214514e24103159aea455147d58b44a8a585, 2b03ebbf8d5e8f6af4ecd6c65375232dd1ec32cc
Linux/Linuxgeneric4.12Not reported
Linux/Linuxgeneric>=a7878ca140084ec267ede48fce64d7e60f6d873e <336b6da10021c69a8f273bbacdf7432fdc89a06f || >=a7878ca140084ec267ede48fce64d7e60f6d873e <5527af72b0100c94287bfec901b6313eeac567ca || >=a7878ca140084ec267ede48fce64d7e60f6d873e <163c16e01f53fc8eb8d0f3484ae6c382265ecbbd || >=a7878ca140084ec267ede48fce64d7e60f6d873e <436a214514e24103159aea455147d58b44a8a585 || >=a7878ca140084ec267ede48fce64d7e60f6d873e <2b03ebbf8d5e8f6af4ecd6c65375232dd1ec32cc336b6da10021c69a8f273bbacdf7432fdc89a06f, 5527af72b0100c94287bfec901b6313eeac567ca, 163c16e01f53fc8eb8d0f3484ae6c382265ecbbd, 436a214514e24103159aea455147d58b44a8a585, 2b03ebbf8d5e8f6af4ecd6c65375232dd1ec32cc
Linux/Linuxgeneric>=a7878ca140084ec267ede48fce64d7e60f6d873e <e55d7fec8a9290f73032ee34c35dd68532809633 || >=a7878ca140084ec267ede48fce64d7e60f6d873e <336b6da10021c69a8f273bbacdf7432fdc89a06f || >=a7878ca140084ec267ede48fce64d7e60f6d873e <5527af72b0100c94287bfec901b6313eeac567ca || >=a7878ca140084ec267ede48fce64d7e60f6d873e <163c16e01f53fc8eb8d0f3484ae6c382265ecbbd || >=a7878ca140084ec267ede48fce64d7e60f6d873e <436a214514e24103159aea455147d58b44a8a585 || >=a7878ca140084ec267ede48fce64d7e60f6d873e <2b03ebbf8d5e8f6af4ecd6c65375232dd1ec32cce55d7fec8a9290f73032ee34c35dd68532809633, 336b6da10021c69a8f273bbacdf7432fdc89a06f, 5527af72b0100c94287bfec901b6313eeac567ca, 163c16e01f53fc8eb8d0f3484ae6c382265ecbbd, 436a214514e24103159aea455147d58b44a8a585, 2b03ebbf8d5e8f6af4ecd6c65375232dd1ec32cc

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 163c16e01f53fc8eb8d0f3484ae6c382265ecbbd; Linux/Linux to 336b6da10021c69a8f273bbacdf7432fdc89a06f; Linux/Linux to e55d7fec8a9290f73032ee34c35dd68532809633 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: NFSv4/flexfiles: fix NULL dereference for NFSv4.0 data servers flexfiles accepts NFSv4.0 data servers, but two NFSv4 code paths assume the data server client has a session. Unlike NFSv4.1+, an NFSv4.0 client has no session (clp->cl_session is NULL; it uses clp->cl_slot_tbl), so I/O to a v4.0 flexfiles DS oopses: - nfs4_init_ds_session() dereferences clp->cl_session->session_state while seeding the DS lease. It also only seeds cl_lease_time when NFS4_SESSION_INITING is set; without a session that never happens, so cl_lease_time stays 0 and nfs4_renew_state() busy-loops, requeuing every 5 seconds. Seed the lease whenever there is no session and return before touching session state. - ff_layout_async_handle_error_v4() dereferences clp->cl_session->fc_slot_table on every DS I/O error. Fall back to the v4.0 transport slot table (clp->cl_slot_tbl) when there is no session.

Quoted source text, attributed separately from HOL analysis.