System crash via unregistered network device double-free
Published Jul 21, 2021 · Updated Aug 4, 2024
Double free in the Linux kernel through 5.13.4 allows physically proximate attackers to crash the system via a crafted USB device. The hso_free_net_device function calls unregister_netdev when the network device never reached NETREG_REGISTERED, releasing the same object twice. Reaching this path requires physical attachment of an Option USB High Speed Mobile device and a device-registration error; the bounded consequence is a kernel crash.
Summary
What happened
Double free in the Linux kernel through 5.13.4 allows physically proximate attackers to crash the system via a crafted USB device. The hso_free_net_device function calls unregister_netdev when the network device never reached NETREG_REGISTERED, releasing the same object twice. Reaching this path requires physical attachment of an Option USB High Speed Mobile device and a device-registration error; the bounded consequence is a kernel crash.
The record
- CVE
- CVE-2021-37159
- Published
- Jul 21, 2021
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-415, CWE-416, T1499
- Attack vector
- physical
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 21, 2021CVE 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
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