CVE-2026-93118: usb: gadget: aspeed_udc: check endpoint DMA allocation
Noroxi assessment
Priority: Monitor (action score 0/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.17% (FIRST EPSS).
- Fixed version: Linux Linux 4aaad88f857498ed1294f061f0b25d27ae891c55, 6182e708e2e1f55521c8a01d7535630ecc2d7df9, 97cee53a94be3bd4fd8fbed6071bd2f32dad1ab1; azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 6.6.157.1-1.
Low priority for now. Upgrade to Linux Linux 4aaad88f857498ed1294f061f0b25d27ae891c55, 6182e708e2e1f55521c8a01d7535630ecc2d7df9, 97cee53a94be3bd4fd8fbed6071bd2f32dad1ab1; azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 6.6.157.1-1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Sep 17, 2026
- Updated
- Oct 19, 2026
- EPSS
- 0.1% · 6th percentile
- CWE
- —
Report tools
Action score
0
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 6.0affected
- 055276c1320564b0192b3af323b8cc67f9b665e1 and later · before d7ae1a48e70e9c3451b7dc7bc3896c82884bc4dfaffected · git
- 055276c1320564b0192b3af323b8cc67f9b665e1 and later · before 4aaad88f857498ed1294f061f0b25d27ae891c55affected · git
- 055276c1320564b0192b3af323b8cc67f9b665e1 and later · before 6182e708e2e1f55521c8a01d7535630ecc2d7df9affected · git
- 055276c1320564b0192b3af323b8cc67f9b665e1 and later · before ff6e88e29965bd06f640e59acdcf0bbf04a7f55caffected · git
- 055276c1320564b0192b3af323b8cc67f9b665e1 and later · before 9e6f57107c1886052d4baaa047a2bc3d0e91be5daffected · git
- 055276c1320564b0192b3af323b8cc67f9b665e1 and later · before 97cee53a94be3bd4fd8fbed6071bd2f32dad1ab1affected · git
- before 6.0not affected · semver
- 6.1.188 and later · up to and including 6.1.*not affected · semver
- 6.6.157 and later · up to and including 6.6.*not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.190-1 | 6.1.190-1 |
| Debian:12 | linux-6.12 | before 6.12.111-1~deb12u1 | 6.12.111-1~deb12u1 |
| Debian:13 | linux | before 6.12.111-1 | 6.12.111-1 |
| Debian:14 | linux | before 7.2.6-1 | 7.2.6-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-93116Sep 17, 2026 · platform/x86: asus-wmi: fix resource leaks on probe failure28Monitor
- ← EarlierCVE-2026-93117Sep 17, 2026 · usb: fix UAF when probe runs concurrent to dyn ID removal0Monitor
- Later →CVE-2026-93119Sep 17, 2026 · usb: ljca: bound bank_num in ljca_enumerate_gpio()0Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 4aaad88f857498ed1294f061f0b25d27ae891c55 | Vendor (CNA) |
| Linux Linux | 6182e708e2e1f55521c8a01d7535630ecc2d7df9 | Vendor (CNA) |
| Linux Linux | 97cee53a94be3bd4fd8fbed6071bd2f32dad1ab1 | Vendor (CNA) |
| Linux Linux | 9e6f57107c1886052d4baaa047a2bc3d0e91be5d | Vendor (CNA) |
| Linux Linux | d7ae1a48e70e9c3451b7dc7bc3896c82884bc4df | Vendor (CNA) |
| Linux Linux | ff6e88e29965bd06f640e59acdcf0bbf04a7f55c | Vendor (CNA) |
| azl3 kernel 6.6.150.1-1 on Azure Linux 3.0 | — | Microsoft (MSRC) |
| azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 | 6.6.157.1-1 · Release Notes | Microsoft (MSRC) |
| debian:linux | 6.1.190-1 · Debian:12 | Package registry (OSV) |
| debian:linux | 6.12.111-1 · Debian:13 | Package registry (OSV) |
| debian:linux-6.12 | 6.12.111-1~deb12u1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Not on record for this CVE: patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
No CVSS vector for this record, so attack conditions can't be derived.
Weakness class (CWE)
—
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (5 more)Show less
- git.kernel.org/stable/c/6182e708e2e1f55521c8a01d7535630ecc2d7df9
- git.kernel.org/stable/c/97cee53a94be3bd4fd8fbed6071bd2f32dad1ab1
- git.kernel.org/stable/c/9e6f57107c1886052d4baaa047a2bc3d0e91be5d
- git.kernel.org/stable/c/d7ae1a48e70e9c3451b7dc7bc3896c82884bc4df
- git.kernel.org/stable/c/ff6e88e29965bd06f640e59acdcf0bbf04a7f55c
Vendor advisories and official records. Exploit/PoC links are deliberately left out.