Memory-exhaustion denial of service via leaked USB buffer
Published Jun 29, 2020 · Updated Aug 4, 2024
Memory leak in the Linux kernel USB testing driver 4.4 through 5.7.6 allows physically proximate attackers to exhaust system memory. usbtest_disconnect frees its device structure without releasing the dev->buf allocation created by usbtest_probe, so each disconnect strands kernel memory. The USB testing driver must be enabled and a USB test device repeatedly connected and disconnected; sustained exhaustion can hang or crash the host.
Summary
What happened
Memory leak in the Linux kernel USB testing driver 4.4 through 5.7.6 allows physically proximate attackers to exhaust system memory. usbtest_disconnect frees its device structure without releasing the dev->buf allocation created by usbtest_probe, so each disconnect strands kernel memory. The USB testing driver must be enabled and a USB test device repeatedly connected and disconnected; sustained exhaustion can hang or crash the host.
The record
- CVE
- CVE-2020-15393
- Published
- Jun 29, 2020
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-401, T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 29, 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.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
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