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 93086 firmware armscmi avoid idr updates while cleaning
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
  • 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-93086

firmware: arm_scmi: Avoid IDR updates while cleaning channelsCVE-2026-93086

Answer in brief

CVE-2026-93086 records a Unknown severity vulnerability in firmware: arm_scmi: Avoid IDR updates while cleaning channels. 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 Sep 17, 2026Updated Oct 30, 2026Source checked Nov 2, 2026First seen by HOL Sep 17, 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
Nov 2, 2026
References
6 linked sources
Open source record

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>=05a2801d8b90c1b5159618d4bd3a3c65d60f3ff1 <aed24a3c63920539e9de7fbfe7929a2e7c888cd2 || >=05a2801d8b90c1b5159618d4bd3a3c65d60f3ff1 <431c6b872ba7fedcc5a3afb0ec3517db4d95d088 || >=05a2801d8b90c1b5159618d4bd3a3c65d60f3ff1 <54e5a4f7d83db4552d963d0785be32d9df680dcd || >=05a2801d8b90c1b5159618d4bd3a3c65d60f3ff1 <bab26acebe55e8ad3ab545abda72faa7ca28c477 || >=05a2801d8b90c1b5159618d4bd3a3c65d60f3ff1 <c38b1e19485aaa820e52cfe162525a8af67563daaed24a3c63920539e9de7fbfe7929a2e7c888cd2, 431c6b872ba7fedcc5a3afb0ec3517db4d95d088, 54e5a4f7d83db4552d963d0785be32d9df680dcd, bab26acebe55e8ad3ab545abda72faa7ca28c477, c38b1e19485aaa820e52cfe162525a8af67563da
Linux/Linuxgeneric6.3Not reported
Linux/Linuxgeneric>=22f7f35fd71b597a5d916e41d7646be6ee530c86 <f50698c617350a6e2064dffd6cff3f391e142f55 || >=05a2801d8b90c1b5159618d4bd3a3c65d60f3ff1 <aed24a3c63920539e9de7fbfe7929a2e7c888cd2 || >=05a2801d8b90c1b5159618d4bd3a3c65d60f3ff1 <431c6b872ba7fedcc5a3afb0ec3517db4d95d088 || >=05a2801d8b90c1b5159618d4bd3a3c65d60f3ff1 <54e5a4f7d83db4552d963d0785be32d9df680dcd || >=05a2801d8b90c1b5159618d4bd3a3c65d60f3ff1 <bab26acebe55e8ad3ab545abda72faa7ca28c477 || >=05a2801d8b90c1b5159618d4bd3a3c65d60f3ff1 <c38b1e19485aaa820e52cfe162525a8af67563daf50698c617350a6e2064dffd6cff3f391e142f55, aed24a3c63920539e9de7fbfe7929a2e7c888cd2, 431c6b872ba7fedcc5a3afb0ec3517db4d95d088, 54e5a4f7d83db4552d963d0785be32d9df680dcd, bab26acebe55e8ad3ab545abda72faa7ca28c477, c38b1e19485aaa820e52cfe162525a8af67563da

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

Evidence timeline and material changes

  1. Published upstream

    Sep 17, 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 17, 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: firmware: arm_scmi: Avoid IDR updates while cleaning channels scmi_cleanup_channels() walks the TX/RX channel IDRs with idr_for_each() to free transport resources and destroy the dedicated transport devices before calling idr_destroy(). The destroy callback removed each entry from the same IDR being walked. That is not needed for this cleanup path, and it is unsafe because idr_for_each() has not advanced its radix-tree iterator while the callback is running. Removing the current entry from the callback can invalidate the iterator state. The callback also cannot be protected by rcu_read_lock(), because scmi_device_destroy() may sleep. Leave IDR teardown to the following idr_destroy() call and keep the callback limited to device destruction.

Quoted source text, attributed separately from HOL analysis.