GHSA-VCJH-87MP-CX8R
Vulnerability from github – Published: 2026-09-17 18:32 – Updated: 2026-09-17 18:32In 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.
{
"affected": [],
"aliases": [
"CVE-2026-93122"
],
"database_specific": {
"cwe_ids": [],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-09-17T17:18:06Z",
"severity": null
},
"details": "In the Linux kernel, the following vulnerability has been resolved:\n\nusb: gadget: uac: validate rate list length before storing\n\nUAC1 and UAC2 configfs rate-list attributes parse a comma-separated\nlist of sampling rates and store each parsed value in fixed-size arrays.\nThe arrays have UAC_MAX_RATES entries, but the store paths do not check\nthat the input contains at most that many tokens before writing through\nopts-\u003ename##s[i++].\n\nWriting more than ten rates therefore writes past the end of the\np_srates[] or c_srates[] array in struct f_uac1_opts or struct\nf_uac2_opts.\n\nWith CONFIG_UBSAN_BOUNDS enabled, writing an 11-entry rate list to the\nUAC1 p_srate attribute reports:\n\n UBSAN: array-index-out-of-bounds\n drivers/usb/gadget/function/f_uac1.c:1669:1\n index 10 is out of range for type \u0027int [10]\u0027\n __ubsan_handle_out_of_bounds.cold\n f_uac1_opts_p_srate_store\n configfs_write_iter\n vfs_write\n ksys_write\n do_syscall_64\n\nThe same reproducer against the UAC2 p_srate attribute reports:\n\n UBSAN: array-index-out-of-bounds\n drivers/usb/gadget/function/f_uac2.c:2087:1\n index 10 is out of range for type \u0027int [10]\u0027\n __ubsan_handle_out_of_bounds.cold\n f_uac2_opts_p_srate_store\n configfs_write_iter\n vfs_write\n ksys_write\n do_syscall_64\n\nReject additional tokens once UAC_MAX_RATES entries have been parsed.\nAlso keep the original kstrdup() pointer for kfree(), because strsep()\nadvances the parsing cursor. Freeing the advanced cursor leaks the\noriginal buffer on successful parses and can free an interior pointer on\nsome error paths.",
"id": "GHSA-vcjh-87mp-cx8r",
"modified": "2026-09-17T18:32:11Z",
"published": "2026-09-17T18:32:11Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-93122"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/3819c6f255a37c4d085ce9f264f9f11bf3c2c6bb"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/844d83d5964b87919b958ff48405188c6ddae9cc"
}
],
"schema_version": "1.4.0",
"severity": []
}
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.