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 64585 can esdusb kill anchored urbs before freeing
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
High · CVSS 7.8CVE-2026-64585

can: esd_usb: kill anchored URBs before freeing netdevsCVE-2026-64585

Answer in brief

CVE-2026-64585 records a High severity (CVSS 7.8) vulnerability in can: esd_usb: kill anchored URBs before freeing netdevs. 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 Aug 6, 2026Updated Aug 23, 2026Source checked Nov 5, 2026First seen by HOL Aug 6, 2026Material review Aug 23, 2026
Upstream Advisory

Record context

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

Key facts

Risk
High · CVSS 7.8
Exploitation
Not marked as known exploited
Affected software
3 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). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
PackageAffected rangeFixed version
Linux/Linuxgeneric>=96d8e90382dc336b5de401164597edfdc2e8d9f1 <aa1d005927db38af783c1a4a8a00a39e0229ab2d || >=96d8e90382dc336b5de401164597edfdc2e8d9f1 <a02e1d8f191324583599544d54e59e6a2b74bb0e || >=96d8e90382dc336b5de401164597edfdc2e8d9f1 <a3314f10369df70925140f59bbe069718f65a0b9 || >=96d8e90382dc336b5de401164597edfdc2e8d9f1 <765ba1c91823a296447528791b89a6504947fd5c || >=96d8e90382dc336b5de401164597edfdc2e8d9f1 <5832c55b3c824ba2fe9c36ac3c411baddcce053e || >=96d8e90382dc336b5de401164597edfdc2e8d9f1 <c43122fef328a70045fe7621c06de6b2b8e19264aa1d005927db38af783c1a4a8a00a39e0229ab2d, a02e1d8f191324583599544d54e59e6a2b74bb0e, a3314f10369df70925140f59bbe069718f65a0b9, 765ba1c91823a296447528791b89a6504947fd5c, 5832c55b3c824ba2fe9c36ac3c411baddcce053e, c43122fef328a70045fe7621c06de6b2b8e19264
Linux/Linuxgeneric2.6.36Not reported
Linux/Linuxgeneric>=96d8e90382dc336b5de401164597edfdc2e8d9f1 <d12f6add48f2da15c8c8281961d3faad804c76cf || >=96d8e90382dc336b5de401164597edfdc2e8d9f1 <aa1d005927db38af783c1a4a8a00a39e0229ab2d || >=96d8e90382dc336b5de401164597edfdc2e8d9f1 <a02e1d8f191324583599544d54e59e6a2b74bb0e || >=96d8e90382dc336b5de401164597edfdc2e8d9f1 <a3314f10369df70925140f59bbe069718f65a0b9 || >=96d8e90382dc336b5de401164597edfdc2e8d9f1 <765ba1c91823a296447528791b89a6504947fd5c || >=96d8e90382dc336b5de401164597edfdc2e8d9f1 <5832c55b3c824ba2fe9c36ac3c411baddcce053e || >=96d8e90382dc336b5de401164597edfdc2e8d9f1 <c43122fef328a70045fe7621c06de6b2b8e19264d12f6add48f2da15c8c8281961d3faad804c76cf, aa1d005927db38af783c1a4a8a00a39e0229ab2d, a02e1d8f191324583599544d54e59e6a2b74bb0e, a3314f10369df70925140f59bbe069718f65a0b9, 765ba1c91823a296447528791b89a6504947fd5c, 5832c55b3c824ba2fe9c36ac3c411baddcce053e, c43122fef328a70045fe7621c06de6b2b8e19264

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

Evidence timeline and material changes

  1. Published upstream

    Aug 6, 2026

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

    Aug 23, 2026

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

    Aug 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
Upstream source description

In the Linux kernel, the following vulnerability has been resolved: can: esd_usb: kill anchored URBs before freeing netdevs esd_usb_disconnect() frees each CAN netdev with free_candev() inside its per-netdev loop and only calls unlink_all_urbs(dev) afterwards. The per-netdev private data (struct esd_usb_net_priv) is embedded in the net_device allocation returned by alloc_candev(), so once free_candev() has run, dev->nets[i] points to freed memory. unlink_all_urbs() then dereferences the freed dev->nets[i] to kill the per-netdev TX anchor (usb_kill_anchored_urbs(&priv->tx_submitted)), clear active_tx_jobs, and reset priv->tx_contexts[]. Reorder the teardown so the anchored URBs are killed before the netdevs are freed, matching other CAN/USB drivers in the same directory such as ems_usb, usb_8dev and mcba_usb, which unregister, then unlink, then free: unregister the netdevs first (which stops their TX queues), call unlink_all_urbs(dev) once, then free the netdevs. This issue was found by an in-house static analysis tool.

Quoted source text, attributed separately from HOL analysis.