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 98773 usb cdc acm skip urb restart in portshutdown if
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
Unknown severity ยท Source severity not reportedCVE-2026-98773

USB: cdc-acm: skip URB restart in port_shutdown if disconnectedCVE-2026-98773

Answer in brief

CVE-2026-98773 records a Unknown severity vulnerability in USB: cdc-acm: skip URB restart in port_shutdown if disconnected. The current sources do not mark it as known exploited. The current feed maps 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 Oct 18, 2026Updated Oct 21, 2026Source checked Oct 25, 2026First seen by HOL Oct 18, 2026Material review Oct 21, 2026
Upstream Advisory

Key facts

Risk
Unknown severitySource severity not reported
Exploitation
Not marked as known exploited
Affected software
3 mapped packages or products
Fix availability
Available

Why this deserves its current priority

A CVSS score is not reported in the current record. 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). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
PackageAffected rangeFixed version
Linux/Linuxgeneric>=603d5a7110832e10165d21f9a1486399457177de <9742905d9ed5bf23ebe4c100dec80b6bc50fb522 || >=5d29d7ff8679e5a525f22da467ba33c042e8029b <a0ed07b5bbb2d8fcef86810453216070691816e7 || >=f58752ebcb35e156c85cd1a82d6579c7af3b9023 <420ca35af891d33522cc08504768ccd60a4c450a || >=f58752ebcb35e156c85cd1a82d6579c7af3b9023 <dc614d6bc991740d41d5a99ac7765c4b675dda88 || d826061aa64cb28089bf4c73e301dd7928662b84 || 8fb82e3555a7d56a05d8ef0edee9859f889c0860 || 283f8162cc3c82086537cbc7dc01870dbeb07a91 || f77f10bc76c2da86b4248269472f6d971e37828b || >=6.12.83 <6.12.113 || >=6.18.24 <6.18.56 || >=6.1.175 <6.2 || >=6.6.136 <6.7 || >=6.19.14 <6.20 || >=7.0.1 <7.19742905d9ed5bf23ebe4c100dec80b6bc50fb522, a0ed07b5bbb2d8fcef86810453216070691816e7, 420ca35af891d33522cc08504768ccd60a4c450a, dc614d6bc991740d41d5a99ac7765c4b675dda88, 6.12.113, 6.18.56, 6.2, 6.7, 6.20, 7.1
Linux/Linuxgeneric7.1Not reported
Linux/Linuxgeneric>=8fb82e3555a7d56a05d8ef0edee9859f889c0860 <d86775e79838d7d2e38ccf506a7d0f8e2dd4d5d0 || >=603d5a7110832e10165d21f9a1486399457177de <9742905d9ed5bf23ebe4c100dec80b6bc50fb522 || >=5d29d7ff8679e5a525f22da467ba33c042e8029b <a0ed07b5bbb2d8fcef86810453216070691816e7 || >=f58752ebcb35e156c85cd1a82d6579c7af3b9023 <420ca35af891d33522cc08504768ccd60a4c450a || >=f58752ebcb35e156c85cd1a82d6579c7af3b9023 <dc614d6bc991740d41d5a99ac7765c4b675dda88 || d826061aa64cb28089bf4c73e301dd7928662b84 || 283f8162cc3c82086537cbc7dc01870dbeb07a91 || f77f10bc76c2da86b4248269472f6d971e37828b || >=6.6.136 <6.6.160 || >=6.12.83 <6.12.113 || >=6.18.24 <6.18.56 || >=6.1.175 <6.2 || >=6.19.14 <6.20 || >=7.0.1 <7.1d86775e79838d7d2e38ccf506a7d0f8e2dd4d5d0, 9742905d9ed5bf23ebe4c100dec80b6bc50fb522, a0ed07b5bbb2d8fcef86810453216070691816e7, 420ca35af891d33522cc08504768ccd60a4c450a, dc614d6bc991740d41d5a99ac7765c4b675dda88, 6.6.160, 6.12.113, 6.18.56, 6.2, 6.20, 7.1

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 9742905d9ed5bf23ebe4c100dec80b6bc50fb522; Linux/Linux to d86775e79838d7d2e38ccf506a7d0f8e2dd4d5d0 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

  1. Published upstream

    Oct 18, 2026

    Evidence: source:cvelist:source_dates:source-dates:record
  2. Source modified

    Oct 21, 2026

    Evidence: source:cvelist:source_dates:source-dates:record
  3. First seen by HOL

    Oct 18, 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
Upstream source description

In the Linux kernel, the following vulnerability has been resolved: USB: cdc-acm: skip URB restart in port_shutdown if disconnected acm_port_shutdown() is called from the tty-port machinery whenever the last user closes the port. acm_disconnect() sets acm->disconnected and calls tty_port_tty_vhangup(), which eventually triggers port_shutdown(). At that point acm_disconnect() has already called acm_poison_urbs() and is about to free the control and read URBs. However, acm_port_shutdown() unconditionally calls acm_unpoison_urbs() and, when the ALWAYS_POLL_CTRL quirk is set, immediately re-submits the ctrlurb and all read URBs. If the concurrent acm_disconnect() then frees those URBs and their DMA buffers while they are in-flight, the result is a use-after-free in acm_ctrl_irq() or acm_read_bulk_callback() accessing the freed DMA memory. Fix by checking acm->disconnected after draining the delayed anchor and returning early: if we are in a disconnect path the URBs must remain poisoned and must not be resubmitted. The early return is placed after the delayed-anchor drain loop because that loop only cancels write-side accounting (wb->use = false and autopm counter) and does not touch the hardware path.

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 25, 2026
References
5 linked sources
Open source record