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 90044 usb gadget ffs fix use after free in aio error
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-90044

usb: gadget: f_fs: Fix Use-After-Free in AIO error pathCVE-2026-90044

Answer in brief

CVE-2026-90044 records a High severity (CVSS 7.8) vulnerability in usb: gadget: f_fs: Fix Use-After-Free in AIO error path. 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
High · CVSS 7.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 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) and additional mapped packages. Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
PackageAffected rangeFixed version
Linux/Linuxgeneric4.0Not reported
Linux/Linuxgeneric>=de2080d41b5d584205e408d72021f0f335a046fc <b5f0e80a03e87bd932487e03248eae3ba3ed7b45 || >=de2080d41b5d584205e408d72021f0f335a046fc <153b5ecd29ed055562400bc17c91df3fd869b0ce || >=de2080d41b5d584205e408d72021f0f335a046fc <4a2fb2d12b87b43724230abb52a1440617c7b6cc || >=de2080d41b5d584205e408d72021f0f335a046fc <e78dcb1f7ec271449c54984dc90c62a5ba272de7b5f0e80a03e87bd932487e03248eae3ba3ed7b45, 153b5ecd29ed055562400bc17c91df3fd869b0ce, 4a2fb2d12b87b43724230abb52a1440617c7b6cc, e78dcb1f7ec271449c54984dc90c62a5ba272de7
Linux/Linuxgeneric>=de2080d41b5d584205e408d72021f0f335a046fc <153b5ecd29ed055562400bc17c91df3fd869b0ce || >=de2080d41b5d584205e408d72021f0f335a046fc <4a2fb2d12b87b43724230abb52a1440617c7b6cc || >=de2080d41b5d584205e408d72021f0f335a046fc <e78dcb1f7ec271449c54984dc90c62a5ba272de7153b5ecd29ed055562400bc17c91df3fd869b0ce, 4a2fb2d12b87b43724230abb52a1440617c7b6cc, e78dcb1f7ec271449c54984dc90c62a5ba272de7
Linux/Linuxgeneric>=de2080d41b5d584205e408d72021f0f335a046fc <0a2f71ccf9c2053de725e9a7922d081f3f3a3804 || >=de2080d41b5d584205e408d72021f0f335a046fc <b5f0e80a03e87bd932487e03248eae3ba3ed7b45 || >=de2080d41b5d584205e408d72021f0f335a046fc <153b5ecd29ed055562400bc17c91df3fd869b0ce || >=de2080d41b5d584205e408d72021f0f335a046fc <4a2fb2d12b87b43724230abb52a1440617c7b6cc || >=de2080d41b5d584205e408d72021f0f335a046fc <e78dcb1f7ec271449c54984dc90c62a5ba272de70a2f71ccf9c2053de725e9a7922d081f3f3a3804, b5f0e80a03e87bd932487e03248eae3ba3ed7b45, 153b5ecd29ed055562400bc17c91df3fd869b0ce, 4a2fb2d12b87b43724230abb52a1440617c7b6cc, e78dcb1f7ec271449c54984dc90c62a5ba272de7
Linux/Linuxgeneric>=de2080d41b5d584205e408d72021f0f335a046fc <922a29e1f8573fd405eea1a73a52112c4e7fcfc4 || >=de2080d41b5d584205e408d72021f0f335a046fc <0a2f71ccf9c2053de725e9a7922d081f3f3a3804 || >=de2080d41b5d584205e408d72021f0f335a046fc <b5f0e80a03e87bd932487e03248eae3ba3ed7b45 || >=de2080d41b5d584205e408d72021f0f335a046fc <153b5ecd29ed055562400bc17c91df3fd869b0ce || >=de2080d41b5d584205e408d72021f0f335a046fc <4a2fb2d12b87b43724230abb52a1440617c7b6cc || >=de2080d41b5d584205e408d72021f0f335a046fc <e78dcb1f7ec271449c54984dc90c62a5ba272de7922a29e1f8573fd405eea1a73a52112c4e7fcfc4, 0a2f71ccf9c2053de725e9a7922d081f3f3a3804, b5f0e80a03e87bd932487e03248eae3ba3ed7b45, 153b5ecd29ed055562400bc17c91df3fd869b0ce, 4a2fb2d12b87b43724230abb52a1440617c7b6cc, e78dcb1f7ec271449c54984dc90c62a5ba272de7

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 b5f0e80a03e87bd932487e03248eae3ba3ed7b45; Linux/Linux to 153b5ecd29ed055562400bc17c91df3fd869b0ce; Linux/Linux to 0a2f71ccf9c2053de725e9a7922d081f3f3a3804; Linux/Linux to 922a29e1f8573fd405eea1a73a52112c4e7fcfc4 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: usb: gadget: f_fs: Fix Use-After-Free in AIO error path In ffs_epfile_write_iter() and ffs_epfile_read_iter(), when ffs_epfile_io() fails with an error other than -EIOCBQUEUED, the io_data structure (`p`) is freed. However, for AIO operations, the kiocb cancel function was already armed and kiocb->private was set to `p`. If a concurrent cancel operation (such as sys_io_cancel()) executes after ffs_epfile_io() fails but before the function frees `p`, a Use-After-Free can occur when the cancellation handler accesses the freed pointer. To securely fix this race condition, we must properly un-arm the cancellation. Invoking `kiocb->ki_complete()` does exactly this by acquiring `ctx->ctx_lock` and safely removing the kiocb from the active sequence. In doing so, it ensures that a parallel io_cancel can no longer discover the kiocb, effectively closing the race window. We then return -EIOCBQUEUED to notify the VFS layer that the kiocb has been consumed and it should avoid attempting to complete the request again or triggering subsequent completion handlers.

Quoted source text, attributed separately from HOL analysis.