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 43432 usb xhci fix memory leak in xhcidisableslot
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
  • Contribute to HOL
  • 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
Unknown severity · Source severity not reportedCVE-2026-43432

usb: xhci: Fix memory leak in xhci_disable_slot()CVE-2026-43432

Answer in brief

CVE-2026-43432 records a Unknown severity vulnerability in usb: xhci: Fix memory leak in xhci_disable_slot(). The current sources do not mark it as known exploited. The current feed maps 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 May 8, 2026Updated Nov 6, 2026Source checked Nov 6, 2026First seen by HOL Nov 6, 2026Material review Nov 6, 2026
Upstream Advisory

Record context

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

Key facts

Risk
Unknown severitySource severity not reported
Exploitation
Not marked as known exploited
Affected software
2 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). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
PackageAffected rangeFixed version
Linux/Linuxgeneric>=fee8be5bde562d4f5f9a100ca80c6d7072ed34c8 <1e800e26d54ccf2ddf2ea6d6cbe021c804d8aa62 || >=02d5a2a48bb44e7404b794df87e57588b2fd604e <6288baf0c8c4dcfbf206773aede9c1f2269cec28 || >=7faac1953ed1f658f719cdf7bb7303fa5eef822c <46aea90763832cd6e9b0c2e1c00e6a9512156d4b || >=7faac1953ed1f658f719cdf7bb7303fa5eef822c <2e2baa8fb5aa4d080cbfeb84c51eff797529f413 || >=7faac1953ed1f658f719cdf7bb7303fa5eef822c <807e4fb5140c73eb5dba1e399a990db5c1f3cdf8 || >=7faac1953ed1f658f719cdf7bb7303fa5eef822c <c65f1b840ab8ce72ba68f1b63bab7960f8fdfa89 || >=7faac1953ed1f658f719cdf7bb7303fa5eef822c <078b446efc0f5e496c31bccb72b98af979963a83 || >=7faac1953ed1f658f719cdf7bb7303fa5eef822c <c1c8550e70401159184130a1afc6261db01fc0ce || cc7c2818c71ebace207df40cc586c8c74e3d1a59 || ec0cddcc2454ab08193beb473978f8f8889b7e24 || >=5.10.85 <5.10.253 || >=5.15.8 <5.15.203 || >=4.19.221 <4.20 || >=5.4.165 <5.51e800e26d54ccf2ddf2ea6d6cbe021c804d8aa62, 6288baf0c8c4dcfbf206773aede9c1f2269cec28, 46aea90763832cd6e9b0c2e1c00e6a9512156d4b, 2e2baa8fb5aa4d080cbfeb84c51eff797529f413, 807e4fb5140c73eb5dba1e399a990db5c1f3cdf8, c65f1b840ab8ce72ba68f1b63bab7960f8fdfa89, 078b446efc0f5e496c31bccb72b98af979963a83, c1c8550e70401159184130a1afc6261db01fc0ce, 5.10.253, 5.15.203, 4.20, 5.5
Linux/Linuxgeneric5.16Not reported

Recommended response

  1. 1Check inventory. Check lockfiles and deployed manifests for Linux/Linux, Linux/Linux.
  2. 2Review the reported fix. Update Linux/Linux to 1e800e26d54ccf2ddf2ea6d6cbe021c804d8aa62 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

  1. Published upstream

    May 8, 2026

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

    Nov 6, 2026

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

    Nov 6, 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
  • Source referencegit.kernel.org
  • Source referencegit.kernel.org
Upstream source description

In the Linux kernel, the following vulnerability has been resolved: usb: xhci: Fix memory leak in xhci_disable_slot() xhci_alloc_command() allocates a command structure and, when the second argument is true, also allocates a completion structure. Currently, the error handling path in xhci_disable_slot() only frees the command structure using kfree(), causing the completion structure to leak. Use xhci_free_command() instead of kfree(). xhci_free_command() correctly frees both the command structure and the associated completion structure. Since the command structure is allocated with zero-initialization, command->in_ctx is NULL and will not be erroneously freed by xhci_free_command(). This bug was found using an experimental static analysis tool we are developing. The tool is based on the LLVM framework and is specifically designed to detect memory management issues. It is currently under active development and not yet publicly available, but we plan to open-source it after our research is published. The bug was originally detected on v6.13-rc1 using our static analysis tool, and we have verified that the issue persists in the latest mainline kernel. We performed build testing on x86_64 with allyesconfig using GCC=11.4.0. Since triggering these error paths in xhci_disable_slot() requires specific hardware conditions or abnormal state, we were unable to construct a test case to reliably trigger these specific error paths at runtime.

Quoted source text, attributed separately from HOL analysis.