usb: gadget: aspeed_udc: check endpoint DMA allocation
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 055276c1320564b0192b3af323b8cc67f9b665e1 · < 97cee53a94be3bd4fd8fbed6071bd2f32dad1ab1| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
usb: gadget: aspeed_udc: check endpoint DMA allocation
ast_udc_probe() allocates a coherent DMA buffer used as the backing store for endpoint buffers. ast_udc_init_ep() derives per-endpoint buffer pointers from udc->ep0_buf, so a failed allocation is dereferenced during probe.
Check the allocation before endpoint setup. The existing probe error path called ast_udc_remove(), which unregisters the gadget unconditionally and is not safe before usb_add_gadget_udc() succeeds. Add a local cleanup helper for probe failures so pre-registration failures only unwind the resources that were actually initialized.
This was found by a local static analysis checker for unchecked allocator returns while scanning Linux 6.16. The change was checked by applying it to current mainline and by running checkpatch. I do not have access to Aspeed UDC hardware, so no runtime testing was performed.
From the CVE record · Linux
The Aspeed USB gadget controller can dereference a failed DMA allocation during device probe, potentially crashing the kernel. The input does not establish whether an attacker can trigger the allocation failure or specify any network, authentication, or user-interaction conditions.
Engineers running Linux kernels with the Aspeed USB gadget controller should check their exposure; affected versions are not specified.