System crash via truncated USB UDC name
Published May 18, 2020 · Updated Aug 4, 2024
Out-of-bounds read in the Linux kernel 3.16 through 5.6.13 allows local users to crash the system via a crafted USB gadget UDC name. The store handler uses the original input length to index a kstrdup-allocated copy that stops at an embedded null byte, so name[len - 1] reads beyond the allocation. Writing the USB gadget UDC configfs attribute and binding a gadget to a controller are required; the demonstrated consequence is a kernel crash.
Summary
What happened
Out-of-bounds read in the Linux kernel 3.16 through 5.6.13 allows local users to crash the system via a crafted USB gadget UDC name. The store handler uses the original input length to index a kstrdup-allocated copy that stops at an embedded null byte, so name[len - 1] reads beyond the allocation. Writing the USB gadget UDC configfs attribute and binding a gadget to a controller are required; the demonstrated consequence is a kernel crash.
The record
- CVE
- CVE-2020-13143
- Published
- May 18, 2020
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-125, T1499
- Attack vector
- local
- Privileges
- Unavailable
Timeline
How it unfolded
- May 18, 2020CVE publishedPublication date reported by the CVE source.
- Aug 4, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
- syzbot USB gadget UDC crash reproducerproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo