usb: gadget: uvc: hold opts->lock across XU walks in uvc_function_bind
Summary
| CVE | CVE-2026-64233 |
| State | PUBLISHED |
| Assigner | Linux |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2026-07-24 16:16:52 UTC |
| Updated | 2026-07-24 16:16:52 UTC |
| Description | In the Linux kernel, the following vulnerability has been resolved:
usb: gadget: uvc: hold opts->lock across XU walks in uvc_function_bind
uvc_function_bind() walks &opts->extension_units twice without holding
opts->lock:
- directly, for the iExtension string-descriptor fixup loop;
- indirectly, four times via uvc_copy_descriptors() (once per speed),
where the helper iterates uvc->desc.extension_units (which aliases
&opts->extension_units) to size and emit XU descriptors.
The configfs side (uvcg_extension_make / uvcg_extension_drop, in
drivers/usb/gadget/function/uvc_configfs.c) takes opts->lock around its
list_add_tail / list_del operations. A privileged userspace process
that holds the configfs subtree open and writes the gadget UDC name
to bind the function while concurrently rmdir()'ing an extensions
subdir can race uvcg_extension_drop() against the bind-time list walks
and dereference a freed struct uvcg_extension.
Hold opts->lock from the start of the XU string-descriptor fixup
through the last uvc_copy_descriptors() call, releasing on the
descriptor-error path via a new error_unlock label that drops the
lock before falling through to the existing error label. This
matches the locking discipline of the configfs callbacks and removes
the only remaining unsynchronised reader of the XU list during bind.
Reachability: only privileged processes that can mount configfs and
write to gadget UDC files can trigger the race, so this is a
correctness fix rather than a security boundary. |
Vendor Declared Affected Products
| Source | Vendor | Product | Version | Platforms |
|---|
| CNA |
Linux |
Linux |
affected 0525210c9840229e42c6b68e886c72a75a67cf8e e15c414092b3c24610cc771e481a723b0f645eca git |
Not specified |
| CNA |
Linux |
Linux |
affected 0525210c9840229e42c6b68e886c72a75a67cf8e 2c9e0905ef7e69f7b814cd709613f6b3b5b98805 git |
Not specified |
| CNA |
Linux |
Linux |
affected 0525210c9840229e42c6b68e886c72a75a67cf8e caec0145e5974e85fe5192fc6a6f5aa1a98f82a6 git |
Not specified |
| CNA |
Linux |
Linux |
affected 0525210c9840229e42c6b68e886c72a75a67cf8e 5f1b9cff88982e2a2053d8b1fd983f7ccb9f03cc git |
Not specified |
| CNA |
Linux |
Linux |
affected 0525210c9840229e42c6b68e886c72a75a67cf8e 68aa70648b625fa684bc0b71bbfd905f4943ca20 git |
Not specified |
| CNA |
Linux |
Linux |
affected 6.3 |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.3 semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.6.143 6.6.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.12.93 6.12.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.18.35 6.18.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 7.0.12 7.0.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 7.1 * original_commit_for_fix |
Not specified |
References
| Reference | Source | Link | Tags |
|---|
| git.kernel.org/stable/c/caec0145e5974e85fe5192fc6a6f5aa1a98f82a6 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/2c9e0905ef7e69f7b814cd709613f6b3b5b98805 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/e15c414092b3c24610cc771e481a723b0f645eca |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/68aa70648b625fa684bc0b71bbfd905f4943ca20 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/5f1b9cff88982e2a2053d8b1fd983f7ccb9f03cc |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| CVE Program record |
CVE.ORG |
www.cve.org |
canonical |
| NVD vulnerability detail |
NVD |
nvd.nist.gov |
canonical, analysis |
No vendor comments have been submitted for this CVE.
There are currently no legacy QID mappings associated with this CVE.