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 93116 platformx86 asus wmi fix resource leaks on probe
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
High · CVSS 7.0CVE-2026-93116

platform/x86: asus-wmi: fix resource leaks on probe failureCVE-2026-93116

Answer in brief

CVE-2026-93116 records a High severity (CVSS 7.0) vulnerability in platform/x86: asus-wmi: fix resource leaks on probe failure. 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
High · CVSS 7.0
Exploitation
Not marked as known exploited
Affected software
5 mapped packages or products
Fix availability
Available

Why this deserves its current priority

CVSS is 7.0. 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>=0f0ac158d28ff78e75c334e869b1cb8e69372a1f <3308b8c5f5a28403611a2f5a46f06aabe4f0c661 || >=0f0ac158d28ff78e75c334e869b1cb8e69372a1f <ef3daa2b84a2b8499ce9e2ce1c865dca36d39f953308b8c5f5a28403611a2f5a46f06aabe4f0c661, ef3daa2b84a2b8499ce9e2ce1c865dca36d39f95
Linux/Linuxgeneric5.17Not reported
Linux/Linuxgeneric>=0f0ac158d28ff78e75c334e869b1cb8e69372a1f <8410cd2690d463b60527d00ac8cffea2d5a041f6 || >=0f0ac158d28ff78e75c334e869b1cb8e69372a1f <3308b8c5f5a28403611a2f5a46f06aabe4f0c661 || >=0f0ac158d28ff78e75c334e869b1cb8e69372a1f <ef3daa2b84a2b8499ce9e2ce1c865dca36d39f958410cd2690d463b60527d00ac8cffea2d5a041f6, 3308b8c5f5a28403611a2f5a46f06aabe4f0c661, ef3daa2b84a2b8499ce9e2ce1c865dca36d39f95
Linux/Linuxgeneric>=0f0ac158d28ff78e75c334e869b1cb8e69372a1f <959ed35f8c8f07b8dd43c3f917a43ae2f77e4471 || >=0f0ac158d28ff78e75c334e869b1cb8e69372a1f <8d5999608da60db45949e5459f74f581cdaacd04 || >=0f0ac158d28ff78e75c334e869b1cb8e69372a1f <8410cd2690d463b60527d00ac8cffea2d5a041f6 || >=0f0ac158d28ff78e75c334e869b1cb8e69372a1f <3308b8c5f5a28403611a2f5a46f06aabe4f0c661 || >=0f0ac158d28ff78e75c334e869b1cb8e69372a1f <ef3daa2b84a2b8499ce9e2ce1c865dca36d39f95959ed35f8c8f07b8dd43c3f917a43ae2f77e4471, 8d5999608da60db45949e5459f74f581cdaacd04, 8410cd2690d463b60527d00ac8cffea2d5a041f6, 3308b8c5f5a28403611a2f5a46f06aabe4f0c661, ef3daa2b84a2b8499ce9e2ce1c865dca36d39f95
Linux/Linuxgeneric>=0f0ac158d28ff78e75c334e869b1cb8e69372a1f <72d792c8053f238ae541fdaa90e609548509b65f || >=0f0ac158d28ff78e75c334e869b1cb8e69372a1f <959ed35f8c8f07b8dd43c3f917a43ae2f77e4471 || >=0f0ac158d28ff78e75c334e869b1cb8e69372a1f <8d5999608da60db45949e5459f74f581cdaacd04 || >=0f0ac158d28ff78e75c334e869b1cb8e69372a1f <8410cd2690d463b60527d00ac8cffea2d5a041f6 || >=0f0ac158d28ff78e75c334e869b1cb8e69372a1f <3308b8c5f5a28403611a2f5a46f06aabe4f0c661 || >=0f0ac158d28ff78e75c334e869b1cb8e69372a1f <ef3daa2b84a2b8499ce9e2ce1c865dca36d39f9572d792c8053f238ae541fdaa90e609548509b65f, 959ed35f8c8f07b8dd43c3f917a43ae2f77e4471, 8d5999608da60db45949e5459f74f581cdaacd04, 8410cd2690d463b60527d00ac8cffea2d5a041f6, 3308b8c5f5a28403611a2f5a46f06aabe4f0c661, ef3daa2b84a2b8499ce9e2ce1c865dca36d39f95

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 3308b8c5f5a28403611a2f5a46f06aabe4f0c661; Linux/Linux to 8410cd2690d463b60527d00ac8cffea2d5a041f6; Linux/Linux to 959ed35f8c8f07b8dd43c3f917a43ae2f77e4471; Linux/Linux to 72d792c8053f238ae541fdaa90e609548509b65f 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: platform/x86: asus-wmi: fix resource leaks on probe failure During driver initialization in asus_wmi_add(), various subsystems are registered sequentially. However, the error path labels are out of order relative to the registration sequence. Specifically: 1. If asus_wmi_custom_fan_curve_init() fails, the driver jumps to fail_custom_fan_curve. Because this label is placed below fail_sysfs, it bypasses the cleanup calls for the input device and sysfs groups, which were successfully registered before, leaking those resources. 2. If asus_screenpad_init() fails, the driver jumps to fail_screenpad. Because fail_screenpad is placed below fail_backlight, it bypasses the cleanup calls for backlight and rfkill, leaking those resources. Fix these resource leaks by reordering the error path labels in asus_wmi_add() to match the exact reverse order of the resource allocations.

Quoted source text, attributed separately from HOL analysis.