Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

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

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.

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 32 days later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.

EPSS (exploitation in 30 days)
0.17% · top 93% of all CVEs (18 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.

Affected products

  • Linux · Linux

    • affected 055276c1320564b0192b3af323b8cc67f9b665e1 – < d7ae1a48e70e9c3451b7dc7bc3896c82884bc4df
    • affected 055276c1320564b0192b3af323b8cc67f9b665e1 – < 4aaad88f857498ed1294f061f0b25d27ae891c55
    • affected 055276c1320564b0192b3af323b8cc67f9b665e1 – < 6182e708e2e1f55521c8a01d7535630ecc2d7df9
    • affected 055276c1320564b0192b3af323b8cc67f9b665e1 – < ff6e88e29965bd06f640e59acdcf0bbf04a7f55c
    • affected 055276c1320564b0192b3af323b8cc67f9b665e1 – < 9e6f57107c1886052d4baaa047a2bc3d0e91be5d
    • affected 055276c1320564b0192b3af323b8cc67f9b665e1 – < 97cee53a94be3bd4fd8fbed6071bd2f32dad1ab1
  • Linux · Linux

    • affected 6.0
    • unaffected < 6.0
    • unaffected 6.1.188 – ≤ 6.1.*
    • unaffected 6.6.157 – ≤ 6.6.*
    • unaffected 6.12.110 – ≤ 6.12.*
    • unaffected 6.18.52 – ≤ 6.18.*
    • unaffected 7.2.6 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References6

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-93118 badge
[![CVE-2026-93118](https://cveledger.app/badge/CVE-2026-93118.svg)](https://cveledger.app/cve/CVE-2026-93118)

Record last updated .