PatchSiren cyber security CVE debrief
CVE-2026-93122 Linux CVE debrief
A Linux kernel vulnerability allows USB gadget users with local access to trigger an out-of-bounds write via the UAC1 and UAC2 configfs rate-list attributes. This issue can lead to a denial of service or potentially code execution. The vulnerability has been resolved with input validation added to reject additional tokens once the maximum rate limit is reached.
- Vendor
- Linux
- Product
- Unknown
- CVSS
- HIGH 7.8
- CISA KEV
- Not listed in stored evidence
- Original CVE published
- 2026-09-17
- Original CVE updated
- 2026-09-18
- Advisory published
- 2026-09-17
- Advisory updated
- 2026-09-18
Who should care
Linux kernel developers and maintainers, Linux distribution vendors, and users of Linux-based systems with USB gadget functionality should assess exposure and apply the patch. System administrators and security teams should monitor for potential exploitation attempts.
Why it matters
CVE-2026-93122 is a Linux kernel vulnerability that allows local attackers to trigger an out-of-bounds write via the UAC1 and UAC2 configfs rate-list attributes. This issue can lead to a denial of service or potentially code execution. Linux kernel developers, maintainers, and users of Linux-based systems with USB gadget functionality should assess exposure and apply the patch.
- Denial of service due to out-of-bounds write
- Potential code execution with elevated privileges
- Increased risk for Linux-based systems with USB gadget functionality
Technical summary
The Linux kernel vulnerability (CVE-2026-93122) occurs in the USB gadget function, specifically in the UAC1 and UAC2 configfs rate-list attributes. These attributes parse a comma-separated list of sampling rates and store each parsed value in fixed-size arrays. However, the store paths do not check that the input contains at most UAC_MAX_RATES entries before writing through opts->name##s[i++]. This allows an attacker with local access to trigger an out-of-bounds write by writing more than ten rates.
Defensive priority
Medium
Recommended defensive actions
- Review and apply the kernel patch to validate rate list length before storing
- Restrict access to the UAC1 and UAC2 configfs rate-list attributes to authorized users
- Monitor for potential exploitation attempts
- Perform vulnerability assessment to identify potential exposure
- Implement compensating controls for exposed systems
- Track changes to Linux kernel configurations and updates
- Review asset inventory for systems with USB gadget functionality
Evidence notes
The CVE record and NVD entry provide details on the vulnerability, including its description and CVSS score. Two source references from the Linux kernel Git repository are also available. The vulnerability allows USB gadget users with local access to trigger an out-of-bounds write via the UAC1 and UAC2 configfs rate-list attributes. This issue can lead to a denial of service or potentially code execution. Linux kernel developers, maintainers, and users of Linux-based systems with USB gadget functionality should assess exposure and to
Sources and references
Verified primary and authoritative sources
-
CVE-2026-93122 CVE Program record
Publisher, destination, and source semantics verified
URL: https://www.cve.org/CVERecord?id=CVE-2026-93122
CVE Program - Official CVE Program record with source-provided CVE metadata.
-
CVE-2026-93122 NVD vulnerability detail
Publisher, destination, and source semantics verified
URL: https://nvd.nist.gov/vuln/detail/CVE-2026-93122
NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.
Supplemental references
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/3819c6f255a37c4d085ce9f264f9f11bf3c2c6bb
416baaa9-dc9f-4396-8d5f-8c081fb06d67
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/844d83d5964b87919b958ff48405188c6ddae9cc
416baaa9-dc9f-4396-8d5f-8c081fb06d67
Methodology and review provenance
AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.