HOL LogoGuard

Explore HOL

  • HOL home
  • AI agent registry
  • AI plugins
  • Open standards
  • HOL members

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.
  • SponsorKeep agent security open: sponsor a project, place a banner, or fund a security initiative.
PricingEnterpriseOpen AppInstall Guard
  1. Guard
  2. Security
  3. CVEs
  4. CVE 2026 80559 input sur40 fix input device registration ordering
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
  • 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-80559

Input: sur40 - fix input device registration orderingCVE-2026-80559

Answer in brief

CVE-2026-80559 records a High severity (CVSS 7.8) vulnerability in Input: sur40 - fix input device registration ordering. 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 26, 2026Updated Aug 27, 2026Source checked Oct 10, 2026First seen by HOL Aug 26, 2026Material review Aug 27, 2026
Upstream Advisory

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>=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <cd4ecce2fd87760c0ad9a9d28c9fc62ea1dbfd3d || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <dab741c9da72102a37cc1020a929051b7c45f9fb || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <764b507be7b51787e1f577ca3bf0bab7efe81ff8 || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <3e8ed76a4f3572e637653f0654cccdf617903231 || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <83aa12f9f2468a4fbef027c09224dc1011850fb0 || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <5c1c5227c93f18cd329dd754b4df5e0e2daece1e || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <beb9b0bd6e6e23f5e9e42b7ef890a50f57f1f3aa || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <9da976eb649c9e2f588a4499410e4d8af687925f || >=0 <5.10.266 || >=0 <5.15.217 || >=0 <6.1.184 || >=0 <6.6.153 || >=0 <6.12.105 || >=0 <6.18.46 || >=0 <7.1.10cd4ecce2fd87760c0ad9a9d28c9fc62ea1dbfd3d, dab741c9da72102a37cc1020a929051b7c45f9fb, 764b507be7b51787e1f577ca3bf0bab7efe81ff8, 3e8ed76a4f3572e637653f0654cccdf617903231, 83aa12f9f2468a4fbef027c09224dc1011850fb0, 5c1c5227c93f18cd329dd754b4df5e0e2daece1e, beb9b0bd6e6e23f5e9e42b7ef890a50f57f1f3aa, 9da976eb649c9e2f588a4499410e4d8af687925f, 5.10.266, 5.15.217, 6.1.184, 6.6.153, 6.12.105, 6.18.46, 7.1.10
Linux/Linuxgeneric>=e831cd251fb91d6c25352d322743db0d17ea11dd <cd4ecce2fd87760c0ad9a9d28c9fc62ea1dbfd3d || >=e831cd251fb91d6c25352d322743db0d17ea11dd <dab741c9da72102a37cc1020a929051b7c45f9fb || >=e831cd251fb91d6c25352d322743db0d17ea11dd <764b507be7b51787e1f577ca3bf0bab7efe81ff8 || >=e831cd251fb91d6c25352d322743db0d17ea11dd <3e8ed76a4f3572e637653f0654cccdf617903231 || >=e831cd251fb91d6c25352d322743db0d17ea11dd <83aa12f9f2468a4fbef027c09224dc1011850fb0 || >=e831cd251fb91d6c25352d322743db0d17ea11dd <5c1c5227c93f18cd329dd754b4df5e0e2daece1e || >=e831cd251fb91d6c25352d322743db0d17ea11dd <beb9b0bd6e6e23f5e9e42b7ef890a50f57f1f3aa || >=e831cd251fb91d6c25352d322743db0d17ea11dd <9da976eb649c9e2f588a4499410e4d8af687925fcd4ecce2fd87760c0ad9a9d28c9fc62ea1dbfd3d, dab741c9da72102a37cc1020a929051b7c45f9fb, 764b507be7b51787e1f577ca3bf0bab7efe81ff8, 3e8ed76a4f3572e637653f0654cccdf617903231, 83aa12f9f2468a4fbef027c09224dc1011850fb0, 5c1c5227c93f18cd329dd754b4df5e0e2daece1e, beb9b0bd6e6e23f5e9e42b7ef890a50f57f1f3aa, 9da976eb649c9e2f588a4499410e4d8af687925f
Linux/Linuxgeneric4.1Not reported

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

Evidence timeline and material changes

  1. Published upstream

    Aug 26, 2026

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

    Aug 27, 2026

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

    Aug 26, 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: Input: sur40 - fix input device registration ordering In sur40_probe(), input_register_device() was previously called early before the V4L2 video device and vb2_queue components were fully initialized. If userspace opened the input device immediately upon registration, sur40_open() would trigger and start the sur40_poll() worker thread. This worker thread invokes sur40_process_video() and accesses the uninitialized vb2_queue structure, leading to a data race and potential system crash. Furthermore, if V4L2 or video registration failed after input_register_device() succeeded, the error path fell through to calling input_free_device() on a successfully registered device instead of input_unregister_device(), corrupting input core state. Move input_register_device() to the very end of sur40_probe(). This ensures the V4L2 and video queue structures are fully initialized before polling can start, and naturally resolves the error path bug since input_free_device() is now only called when input registration has not yet occurred. To maintain strict LIFO (Last-In, First-Out) teardown ordering, also move input_unregister_device() to the very beginning of sur40_disconnect(). This guarantees that the input polling worker thread is stopped before V4L2 video components or control handlers are unregistered.

Quoted source text, attributed separately from HOL analysis.

Related CVEs

  • ExtUtils::Typemaps::STL::Vector versions before 1.05 for Perl allocate a 32 GiB array on an empty listSame generic ecosystem
  • WordPress Forminator plugin <= 1.57.3 - Cross Site Scripting (XSS) vulnerabilitySame generic ecosystem
  • WordPress Thank You Page Customizer for WooCommerce plugin <= 1.2.3 - Content Injection vulnerabilitySame generic ecosystem
  • WordPress GIFT4U plugin <= 1.1.3 - Broken Access Control vulnerabilitySame generic ecosystem
  • Apache DataSketches: datasketches-cpp: Out-of-bounds read in VarOpt union deserialization allows denial of service via a truncated sketchSame generic ecosystem
  • WordPress AFFI – Affiliate Marketing for WooCommerce plugin <= 1.0.10 - PHP Object Injection vulnerabilitySame generic ecosystem

Record context

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