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 80861 usb xhci bail out of setup if the controller is
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-80861

usb: xhci: bail out of setup if the controller is inaccessibleCVE-2026-80861

Answer in brief

CVE-2026-80861 records a Unknown severity vulnerability in usb: xhci: bail out of setup if the controller is inaccessible. 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 4, 2026Updated Oct 19, 2026Source checked Oct 19, 2026First seen by HOL Sep 4, 2026Material review Oct 19, 2026
Upstream Advisory

Record context

Vulnerability class
Vulnerability
EPSS
Not reported
CWE IDs
Not reported
Source
CVE List V5
Source checked
Oct 19, 2026
References
6 linked sources
Open source record

Key facts

Risk
Unknown severitySource severity not reported
Exploitation
Not marked as known exploited
Affected software
5 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), 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/Linuxgeneric>=66d4eadd8d067269ea8fead1a50fe87c2979a80d <301f4a3303b21ea959a8294518ee883710498ac2 || >=66d4eadd8d067269ea8fead1a50fe87c2979a80d <70706dbcf122940f4e3595d7ba1445004cc00074 || >=66d4eadd8d067269ea8fead1a50fe87c2979a80d <c051f66b621695ad7c8438a9497d79e1f4f05edb || >=66d4eadd8d067269ea8fead1a50fe87c2979a80d <bf84c6b0264947794fa783c324a6d874ca6657d8 || >=66d4eadd8d067269ea8fead1a50fe87c2979a80d <0b31744f70c5e06cce5fb660e02d057a3b9e0e37 || >=66d4eadd8d067269ea8fead1a50fe87c2979a80d <78203d5b54a40f0e36196ebf31c9c7a380fc8811301f4a3303b21ea959a8294518ee883710498ac2, 70706dbcf122940f4e3595d7ba1445004cc00074, c051f66b621695ad7c8438a9497d79e1f4f05edb, bf84c6b0264947794fa783c324a6d874ca6657d8, 0b31744f70c5e06cce5fb660e02d057a3b9e0e37, 78203d5b54a40f0e36196ebf31c9c7a380fc8811
Linux/Linuxgeneric2.6.31Not reported
Linux/Linuxgeneric>=66d4eadd8d067269ea8fead1a50fe87c2979a80d <bf84c6b0264947794fa783c324a6d874ca6657d8 || >=66d4eadd8d067269ea8fead1a50fe87c2979a80d <0b31744f70c5e06cce5fb660e02d057a3b9e0e37 || >=66d4eadd8d067269ea8fead1a50fe87c2979a80d <78203d5b54a40f0e36196ebf31c9c7a380fc8811bf84c6b0264947794fa783c324a6d874ca6657d8, 0b31744f70c5e06cce5fb660e02d057a3b9e0e37, 78203d5b54a40f0e36196ebf31c9c7a380fc8811
Linux/Linuxgeneric>=66d4eadd8d067269ea8fead1a50fe87c2979a80d <c051f66b621695ad7c8438a9497d79e1f4f05edb || >=66d4eadd8d067269ea8fead1a50fe87c2979a80d <bf84c6b0264947794fa783c324a6d874ca6657d8 || >=66d4eadd8d067269ea8fead1a50fe87c2979a80d <0b31744f70c5e06cce5fb660e02d057a3b9e0e37 || >=66d4eadd8d067269ea8fead1a50fe87c2979a80d <78203d5b54a40f0e36196ebf31c9c7a380fc8811c051f66b621695ad7c8438a9497d79e1f4f05edb, bf84c6b0264947794fa783c324a6d874ca6657d8, 0b31744f70c5e06cce5fb660e02d057a3b9e0e37, 78203d5b54a40f0e36196ebf31c9c7a380fc8811
Linux/Linuxgeneric>=66d4eadd8d067269ea8fead1a50fe87c2979a80d <70706dbcf122940f4e3595d7ba1445004cc00074 || >=66d4eadd8d067269ea8fead1a50fe87c2979a80d <c051f66b621695ad7c8438a9497d79e1f4f05edb || >=66d4eadd8d067269ea8fead1a50fe87c2979a80d <bf84c6b0264947794fa783c324a6d874ca6657d8 || >=66d4eadd8d067269ea8fead1a50fe87c2979a80d <0b31744f70c5e06cce5fb660e02d057a3b9e0e37 || >=66d4eadd8d067269ea8fead1a50fe87c2979a80d <78203d5b54a40f0e36196ebf31c9c7a380fc881170706dbcf122940f4e3595d7ba1445004cc00074, c051f66b621695ad7c8438a9497d79e1f4f05edb, bf84c6b0264947794fa783c324a6d874ca6657d8, 0b31744f70c5e06cce5fb660e02d057a3b9e0e37, 78203d5b54a40f0e36196ebf31c9c7a380fc8811

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 301f4a3303b21ea959a8294518ee883710498ac2; Linux/Linux to bf84c6b0264947794fa783c324a6d874ca6657d8; Linux/Linux to c051f66b621695ad7c8438a9497d79e1f4f05edb; Linux/Linux to 70706dbcf122940f4e3595d7ba1445004cc00074 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

  1. Published upstream

    Sep 4, 2026

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

    Oct 19, 2026

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

    Sep 4, 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: xhci: bail out of setup if the controller is inaccessible xhci_gen_setup() locates the operational registers using the capability length read from the very first register: xhci->op_regs = hcd->regs + HC_LENGTH(readl(&xhci->cap_regs->hc_capbase)); If the controller is dead or has dropped off the bus, that read returns ~0, HC_LENGTH() truncates it to 0xff, and op_regs ends up 0xff bytes past the page-aligned MMIO base, i.e. unaligned. The first access through it, xhci_halt() -> xhci_handshake() reading op_regs->status, is then an unaligned readl() on device memory. arm64 faults on unaligned device accesses, so instead of xhci_handshake() catching the all-ones value and returning -ENODEV, setup oopses: xhci-pci-renesas 0005:08:00.0: Unable to change power state from D3cold to D0, device inaccessible xhci-pci-renesas 0005:08:00.0: xHCI Host Controller xhci-pci-renesas 0005:08:00.0: new USB bus registered, assigned bus number 1 Unable to handle kernel paging request at virtual address ffff80030a770103 ESR = 0x0000000096000021 FSC = 0x21: alignment fault Internal error: Oops: 0000000096000021 [#1] SMP pc : xhci_halt [xhci_hcd] Call trace: xhci_halt xhci_gen_setup xhci_pci_setup usb_add_hcd usb_hcd_pci_probe xhci_pci_common_probe xhci_pci_renesas_probe This was hit with a Renesas uPD720201 that failed to power up ("Unable to change power state from D3cold to D0, device inaccessible") yet still reached the HCD probe path. Read the capability register once, and if it reads back the all-ones value (as xhci_handshake() and xhci_reset() already test for), abort setup with -ENODEV before op_regs is derived from it. Reading it once also avoids re-reading a register that may change under a concurrent hot-removal.

Quoted source text, attributed separately from HOL analysis.