Skip to main content
VulnerabilityPublished Updated

CVE-2026-93118: Linux kernel · usb: gadget: aspeed_udc: check endpoint DMA allocation

Affects Linux kernelSource CVE Database V5

0

Not known to be exploited · fixed in ff6e88e29965bd06f640e59acdcf0bbf04a7f55c : update Linux kernel when convenient.

Data as of 26 Oct 2026, 13:47 UTC

Severity
Unrated

Rated by Threat Radar · CVSS not yet scored by NVD

EPSS
0.1% chance of exploitation in 30 days – higher than 6% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in ff6e88e29965bd06f640e59acdcf0bbf04a7f55c, d7ae1a48e70e9c3451b7dc7bc3896c82884bc4df, 6182e708e2e1f55521c8a01d7535630ecc2d7df9 +3

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 17 Sep 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ 055276c1320564b0192b3af323b8cc67f9b665e1, < ff6e88e29965bd06f640e59acdcf0bbf04a7f55c
Fixed in
  • ff6e88e29965bd06f640e59acdcf0bbf04a7f55c
LinuxLinuxAffected
  • ≥ 055276c1320564b0192b3af323b8cc67f9b665e1, < d7ae1a48e70e9c3451b7dc7bc3896c82884bc4df
Fixed in
  • d7ae1a48e70e9c3451b7dc7bc3896c82884bc4df
LinuxLinuxAffected
  • ≥ 055276c1320564b0192b3af323b8cc67f9b665e1, < 6182e708e2e1f55521c8a01d7535630ecc2d7df9
Fixed in
  • 6182e708e2e1f55521c8a01d7535630ecc2d7df9
LinuxLinuxAffected
  • ≥ 055276c1320564b0192b3af323b8cc67f9b665e1, < 97cee53a94be3bd4fd8fbed6071bd2f32dad1ab1
Fixed in
  • 97cee53a94be3bd4fd8fbed6071bd2f32dad1ab1
LinuxLinuxAffected
  • ≥ 055276c1320564b0192b3af323b8cc67f9b665e1, < 9e6f57107c1886052d4baaa047a2bc3d0e91be5d
Fixed in
  • 9e6f57107c1886052d4baaa047a2bc3d0e91be5d
LinuxLinuxAffected
  • ≥ 055276c1320564b0192b3af323b8cc67f9b665e1, < 4aaad88f857498ed1294f061f0b25d27ae891c55
Fixed in
  • 4aaad88f857498ed1294f061f0b25d27ae891c55

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.

References

Community reviews

Loading reviews…