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 93122 usb gadget uac validate rate list length before
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.8CVE-2026-93122

usb: gadget: uac: validate rate list length before storingCVE-2026-93122

Answer in brief

CVE-2026-93122 records a High severity (CVSS 7.8) vulnerability in usb: gadget: uac: validate rate list length before storing. 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 2, 2026First seen by HOL Sep 17, 2026Material review Oct 30, 2026
Upstream Advisory

Record context

Vulnerability class
Secret Exfiltration
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
High · CVSS 7.8
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.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), 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>=a7339e4f5788bd088bb0be1f96a6cce459676ed0 <3819c6f255a37c4d085ce9f264f9f11bf3c2c6bb || >=a7339e4f5788bd088bb0be1f96a6cce459676ed0 <844d83d5964b87919b958ff48405188c6ddae9cc3819c6f255a37c4d085ce9f264f9f11bf3c2c6bb, 844d83d5964b87919b958ff48405188c6ddae9cc
Linux/Linuxgeneric5.18Not reported
Linux/Linuxgeneric>=a7339e4f5788bd088bb0be1f96a6cce459676ed0 <0203146ad450932c2d3132e367a99c49efe3122d || >=a7339e4f5788bd088bb0be1f96a6cce459676ed0 <3819c6f255a37c4d085ce9f264f9f11bf3c2c6bb || >=a7339e4f5788bd088bb0be1f96a6cce459676ed0 <844d83d5964b87919b958ff48405188c6ddae9cc0203146ad450932c2d3132e367a99c49efe3122d, 3819c6f255a37c4d085ce9f264f9f11bf3c2c6bb, 844d83d5964b87919b958ff48405188c6ddae9cc
Linux/Linuxgeneric>=a7339e4f5788bd088bb0be1f96a6cce459676ed0 <72888d54bae3677ecd4ba9793b7fd27ba0b27862 || >=a7339e4f5788bd088bb0be1f96a6cce459676ed0 <0c2710a36b41bf8defba83c395b99eb1660e9e9a || >=a7339e4f5788bd088bb0be1f96a6cce459676ed0 <0203146ad450932c2d3132e367a99c49efe3122d || >=a7339e4f5788bd088bb0be1f96a6cce459676ed0 <3819c6f255a37c4d085ce9f264f9f11bf3c2c6bb || >=a7339e4f5788bd088bb0be1f96a6cce459676ed0 <844d83d5964b87919b958ff48405188c6ddae9cc72888d54bae3677ecd4ba9793b7fd27ba0b27862, 0c2710a36b41bf8defba83c395b99eb1660e9e9a, 0203146ad450932c2d3132e367a99c49efe3122d, 3819c6f255a37c4d085ce9f264f9f11bf3c2c6bb, 844d83d5964b87919b958ff48405188c6ddae9cc
Linux/Linuxgeneric>=a7339e4f5788bd088bb0be1f96a6cce459676ed0 <30b3b3494000aa01fc8f08bf07ed503c9fde4895 || >=a7339e4f5788bd088bb0be1f96a6cce459676ed0 <72888d54bae3677ecd4ba9793b7fd27ba0b27862 || >=a7339e4f5788bd088bb0be1f96a6cce459676ed0 <0c2710a36b41bf8defba83c395b99eb1660e9e9a || >=a7339e4f5788bd088bb0be1f96a6cce459676ed0 <0203146ad450932c2d3132e367a99c49efe3122d || >=a7339e4f5788bd088bb0be1f96a6cce459676ed0 <3819c6f255a37c4d085ce9f264f9f11bf3c2c6bb || >=a7339e4f5788bd088bb0be1f96a6cce459676ed0 <844d83d5964b87919b958ff48405188c6ddae9cc30b3b3494000aa01fc8f08bf07ed503c9fde4895, 72888d54bae3677ecd4ba9793b7fd27ba0b27862, 0c2710a36b41bf8defba83c395b99eb1660e9e9a, 0203146ad450932c2d3132e367a99c49efe3122d, 3819c6f255a37c4d085ce9f264f9f11bf3c2c6bb, 844d83d5964b87919b958ff48405188c6ddae9cc

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 3819c6f255a37c4d085ce9f264f9f11bf3c2c6bb; Linux/Linux to 0203146ad450932c2d3132e367a99c49efe3122d; Linux/Linux to 72888d54bae3677ecd4ba9793b7fd27ba0b27862; Linux/Linux to 30b3b3494000aa01fc8f08bf07ed503c9fde4895 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: usb: gadget: uac: validate rate list length before storing UAC1 and UAC2 configfs rate-list attributes parse a comma-separated list of sampling rates and store each parsed value in fixed-size arrays. The arrays have UAC_MAX_RATES entries, but the store paths do not check that the input contains at most that many tokens before writing through opts->name##s[i++]. Writing more than ten rates therefore writes past the end of the p_srates[] or c_srates[] array in struct f_uac1_opts or struct f_uac2_opts. With CONFIG_UBSAN_BOUNDS enabled, writing an 11-entry rate list to the UAC1 p_srate attribute reports: UBSAN: array-index-out-of-bounds drivers/usb/gadget/function/f_uac1.c:1669:1 index 10 is out of range for type 'int [10]' __ubsan_handle_out_of_bounds.cold f_uac1_opts_p_srate_store configfs_write_iter vfs_write ksys_write do_syscall_64 The same reproducer against the UAC2 p_srate attribute reports: UBSAN: array-index-out-of-bounds drivers/usb/gadget/function/f_uac2.c:2087:1 index 10 is out of range for type 'int [10]' __ubsan_handle_out_of_bounds.cold f_uac2_opts_p_srate_store configfs_write_iter vfs_write ksys_write do_syscall_64 Reject additional tokens once UAC_MAX_RATES entries have been parsed. Also keep the original kstrdup() pointer for kfree(), because strsep() advances the parsing cursor. Freeing the advanced cursor leaks the original buffer on successful parses and can free an interior pointer on some error paths.

Quoted source text, attributed separately from HOL analysis.