# CVE-2026-93118: usb: gadget: aspeed_udc: check endpoint DMA allocation

> A missing check for DMA allocation failure in the Aspeed UDC driver causes a null pointer dereference during probe, leading to a denial of service.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 17 Sep 2026
- **Updated:** 19 Oct 2026
- **Also known as:** AZL-102150, BELL-CVE-2026-93118, DEBIAN-CVE-2026-93118, GHSA-m596-7j6r-7chf, UBUNTU-CVE-2026-93118

## What is CVE-2026-93118?

CVE-2026-93118 is a vulnerability in Linux, published on 17 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official 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.

## Which versions are affected by CVE-2026-93118?


## How do I fix CVE-2026-93118?

Apply the vendor's patch.

## Is CVE-2026-93118 being exploited?

There is no known exploitation of CVE-2026-93118 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-93118 and fix it if it is affected.

What it is: CVE-2026-93118 is a vulnerability in Linux, published on 17 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-93118 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-93118/ (Markdown: https://insights.sbomify.com/CVE-2026-93118/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-93118
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-93118
- OSV: https://osv.dev/vulnerability/CVE-2026-93118

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-93118/
Summaries are generated and may contain mistakes; the official description above is the record.