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 93081 firmware armscmi fix scmi device destroy lifetimes
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-93081

firmware: arm_scmi: Fix SCMI device destroy lifetimesCVE-2026-93081

Answer in brief

CVE-2026-93081 records a Unknown severity vulnerability in firmware: arm_scmi: Fix SCMI device destroy lifetimes. 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 17, 2026Updated Oct 30, 2026Source checked Nov 1, 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 1, 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>=9ca67840c0ddf3f39407339624cef824a4f27599 <c59b3393df1348a12308aaabd5fbc58ed6b21cf5 || >=9ca67840c0ddf3f39407339624cef824a4f27599 <6abe8fe36b29ff51d1a42c2f338972883f4751a5 || 91ff1e9652fb9beb0174267d6bb38243dff211bb || ff4273d47da81b95ed9396110bcbd1b7b7470fe8 || 2fbf6c9695ad9f05e7e5c166bf43fac7cb3276b3 || 969d8beaa2e374387bf9aa5602ef84fc50bb48d8 || 8a8a3547d5c4960da053df49c75bf623827a25da || >=5.15.182 <5.16 || >=6.1.138 <6.2 || >=6.6.90 <6.7 || >=6.12.28 <6.13 || >=6.14.6 <6.15c59b3393df1348a12308aaabd5fbc58ed6b21cf5, 6abe8fe36b29ff51d1a42c2f338972883f4751a5, 5.16, 6.2, 6.7, 6.13, 6.15
Linux/Linuxgeneric6.15Not reported
Linux/Linuxgeneric>=9ca67840c0ddf3f39407339624cef824a4f27599 <a60bc2df2d323cc1342f0cf95563cae266801e20 || >=9ca67840c0ddf3f39407339624cef824a4f27599 <c59b3393df1348a12308aaabd5fbc58ed6b21cf5 || >=9ca67840c0ddf3f39407339624cef824a4f27599 <6abe8fe36b29ff51d1a42c2f338972883f4751a5 || 91ff1e9652fb9beb0174267d6bb38243dff211bb || ff4273d47da81b95ed9396110bcbd1b7b7470fe8 || 2fbf6c9695ad9f05e7e5c166bf43fac7cb3276b3 || 969d8beaa2e374387bf9aa5602ef84fc50bb48d8 || 8a8a3547d5c4960da053df49c75bf623827a25da || >=5.15.182 <5.16 || >=6.1.138 <6.2 || >=6.6.90 <6.7 || >=6.12.28 <6.13 || >=6.14.6 <6.15a60bc2df2d323cc1342f0cf95563cae266801e20, c59b3393df1348a12308aaabd5fbc58ed6b21cf5, 6abe8fe36b29ff51d1a42c2f338972883f4751a5, 5.16, 6.2, 6.7, 6.13, 6.15
Linux/Linuxgeneric>=2fbf6c9695ad9f05e7e5c166bf43fac7cb3276b3 <d8ecdceeb90cd2c265b222a7b65487faf68fea73 || >=969d8beaa2e374387bf9aa5602ef84fc50bb48d8 <916e27f71a80f6d77c48d1a1a5782d6d5ef9017c || >=9ca67840c0ddf3f39407339624cef824a4f27599 <a60bc2df2d323cc1342f0cf95563cae266801e20 || >=9ca67840c0ddf3f39407339624cef824a4f27599 <c59b3393df1348a12308aaabd5fbc58ed6b21cf5 || >=9ca67840c0ddf3f39407339624cef824a4f27599 <6abe8fe36b29ff51d1a42c2f338972883f4751a5 || 91ff1e9652fb9beb0174267d6bb38243dff211bb || ff4273d47da81b95ed9396110bcbd1b7b7470fe8 || 8a8a3547d5c4960da053df49c75bf623827a25da || >=6.6.90 <6.6.160 || >=6.12.28 <6.12.114 || >=5.15.182 <5.16 || >=6.1.138 <6.2 || >=6.14.6 <6.15d8ecdceeb90cd2c265b222a7b65487faf68fea73, 916e27f71a80f6d77c48d1a1a5782d6d5ef9017c, a60bc2df2d323cc1342f0cf95563cae266801e20, c59b3393df1348a12308aaabd5fbc58ed6b21cf5, 6abe8fe36b29ff51d1a42c2f338972883f4751a5, 6.6.160, 6.12.114, 5.16, 6.2, 6.15
Linux/Linuxgeneric>=ff4273d47da81b95ed9396110bcbd1b7b7470fe8 <afe5c022a180e0ade394d3fffbafc1a701f50993 || >=2fbf6c9695ad9f05e7e5c166bf43fac7cb3276b3 <d8ecdceeb90cd2c265b222a7b65487faf68fea73 || >=969d8beaa2e374387bf9aa5602ef84fc50bb48d8 <916e27f71a80f6d77c48d1a1a5782d6d5ef9017c || >=9ca67840c0ddf3f39407339624cef824a4f27599 <a60bc2df2d323cc1342f0cf95563cae266801e20 || >=9ca67840c0ddf3f39407339624cef824a4f27599 <c59b3393df1348a12308aaabd5fbc58ed6b21cf5 || >=9ca67840c0ddf3f39407339624cef824a4f27599 <6abe8fe36b29ff51d1a42c2f338972883f4751a5 || 91ff1e9652fb9beb0174267d6bb38243dff211bb || 8a8a3547d5c4960da053df49c75bf623827a25da || >=6.1.138 <6.1.191 || >=6.6.90 <6.6.160 || >=6.12.28 <6.12.114 || >=5.15.182 <5.16 || >=6.14.6 <6.15afe5c022a180e0ade394d3fffbafc1a701f50993, d8ecdceeb90cd2c265b222a7b65487faf68fea73, 916e27f71a80f6d77c48d1a1a5782d6d5ef9017c, a60bc2df2d323cc1342f0cf95563cae266801e20, c59b3393df1348a12308aaabd5fbc58ed6b21cf5, 6abe8fe36b29ff51d1a42c2f338972883f4751a5, 6.1.191, 6.6.160, 6.12.114, 5.16, 6.15

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 c59b3393df1348a12308aaabd5fbc58ed6b21cf5; Linux/Linux to a60bc2df2d323cc1342f0cf95563cae266801e20; Linux/Linux to d8ecdceeb90cd2c265b222a7b65487faf68fea73; Linux/Linux to afe5c022a180e0ade394d3fffbafc1a701f50993 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: Fix SCMI device destroy lifetimes scmi_child_dev_find() drops the reference returned by device_find_child() before returning the scmi_device pointer. A concurrent unregister can then release the device while the destroy path is still using the returned pointer. Make the lookup helper return the device_find_child() reference and keep it until scmi_device_destroy() has finished unregistering the child. Also split device_unregister() in __scmi_device_destroy() so the SCMI bus ID is not made reusable until after device_del() has removed the old scmi_dev.N name from sysfs. This avoids a new SCMI device reusing the same ID while the old device is still registered. The final device release callback is also a possible cleanup path when SCMI children are deleted by driver core recursion rather than __scmi_device_destroy(). Release the SCMI bus ID from a common helper used by destroy, register-failure and final-release paths, and clear scmi_dev->id after freeing it so the final release cannot free the same ID again.

Quoted source text, attributed separately from HOL analysis.