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 90330 hid logitech hidpp fix ff device cleanup on init
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-90330

HID: logitech-hidpp: Fix FF device cleanup on init failureCVE-2026-90330

Answer in brief

CVE-2026-90330 records a Unknown severity vulnerability in HID: logitech-hidpp: Fix FF device cleanup on init 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
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>=ff21a635dd1a9c6ca378847160897649cdbbfae4 <13378c9ac0a1bcdf49ba158e4199594aafb589cd || >=ff21a635dd1a9c6ca378847160897649cdbbfae4 <dd5be4d9ce2dfc4d4a4527ef7d31d21a78e3cdac13378c9ac0a1bcdf49ba158e4199594aafb589cd, dd5be4d9ce2dfc4d4a4527ef7d31d21a78e3cdac
Linux/Linuxgeneric4.6Not reported
Linux/Linuxgeneric>=ff21a635dd1a9c6ca378847160897649cdbbfae4 <2fd9c8112907c14efefe6a90d20b774737052db3 || >=ff21a635dd1a9c6ca378847160897649cdbbfae4 <13378c9ac0a1bcdf49ba158e4199594aafb589cd || >=ff21a635dd1a9c6ca378847160897649cdbbfae4 <dd5be4d9ce2dfc4d4a4527ef7d31d21a78e3cdac2fd9c8112907c14efefe6a90d20b774737052db3, 13378c9ac0a1bcdf49ba158e4199594aafb589cd, dd5be4d9ce2dfc4d4a4527ef7d31d21a78e3cdac
Linux/Linuxgeneric>=ff21a635dd1a9c6ca378847160897649cdbbfae4 <360a49fc53acdfe2dbb80c23cfa606ed7e13a85d || >=ff21a635dd1a9c6ca378847160897649cdbbfae4 <6bb216586a3cb4ce327511a7c0445fa88e85b3cb || >=ff21a635dd1a9c6ca378847160897649cdbbfae4 <2fd9c8112907c14efefe6a90d20b774737052db3 || >=ff21a635dd1a9c6ca378847160897649cdbbfae4 <13378c9ac0a1bcdf49ba158e4199594aafb589cd || >=ff21a635dd1a9c6ca378847160897649cdbbfae4 <dd5be4d9ce2dfc4d4a4527ef7d31d21a78e3cdac360a49fc53acdfe2dbb80c23cfa606ed7e13a85d, 6bb216586a3cb4ce327511a7c0445fa88e85b3cb, 2fd9c8112907c14efefe6a90d20b774737052db3, 13378c9ac0a1bcdf49ba158e4199594aafb589cd, dd5be4d9ce2dfc4d4a4527ef7d31d21a78e3cdac
Linux/Linuxgeneric>=ff21a635dd1a9c6ca378847160897649cdbbfae4 <a265fee3d24bd611783fd929582b7b6d62000a65 || >=ff21a635dd1a9c6ca378847160897649cdbbfae4 <360a49fc53acdfe2dbb80c23cfa606ed7e13a85d || >=ff21a635dd1a9c6ca378847160897649cdbbfae4 <6bb216586a3cb4ce327511a7c0445fa88e85b3cb || >=ff21a635dd1a9c6ca378847160897649cdbbfae4 <2fd9c8112907c14efefe6a90d20b774737052db3 || >=ff21a635dd1a9c6ca378847160897649cdbbfae4 <13378c9ac0a1bcdf49ba158e4199594aafb589cd || >=ff21a635dd1a9c6ca378847160897649cdbbfae4 <dd5be4d9ce2dfc4d4a4527ef7d31d21a78e3cdaca265fee3d24bd611783fd929582b7b6d62000a65, 360a49fc53acdfe2dbb80c23cfa606ed7e13a85d, 6bb216586a3cb4ce327511a7c0445fa88e85b3cb, 2fd9c8112907c14efefe6a90d20b774737052db3, 13378c9ac0a1bcdf49ba158e4199594aafb589cd, dd5be4d9ce2dfc4d4a4527ef7d31d21a78e3cdac

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 13378c9ac0a1bcdf49ba158e4199594aafb589cd; Linux/Linux to 2fd9c8112907c14efefe6a90d20b774737052db3; Linux/Linux to 360a49fc53acdfe2dbb80c23cfa606ed7e13a85d; Linux/Linux to a265fee3d24bd611783fd929582b7b6d62000a65 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: HID: logitech-hidpp: Fix FF device cleanup on init failure hidpp_ff_init() creates the input force-feedback device with input_ff_create(), then allocates the HID++ FF private data, effect ID array, and workqueue. If any of those allocations fail after input_ff_create() succeeds, the function returns an error without destroying the FF device. Add an unwind path that frees the private allocations made by hidpp_ff_init() and calls input_ff_destroy() for failures after input_ff_create() succeeds.

Quoted source text, attributed separately from HOL analysis.