Local service interruption via KVM device leaks
Published Apr 6, 2021 · Updated Aug 4, 2024
Memory leak in Linux kernel before 5.8.10 allows local users to exhaust memory through KVM device-bus unregistration. When kmalloc cannot allocate a smaller bus in kvm_io_bus_unregister_dev, the failure path removes the bus without calling kvm_iodevice_destructor on its other devices. Low-privileged local access is required, and repeated triggering can interrupt service by exhausting kernel memory.
Summary
What happened
Memory leak in Linux kernel before 5.8.10 allows local users to exhaust memory through KVM device-bus unregistration. When kmalloc cannot allocate a smaller bus in kvm_io_bus_unregister_dev, the failure path removes the bus without calling kvm_iodevice_destructor on its other devices. Low-privileged local access is required, and repeated triggering can interrupt service by exhausting kernel memory.
The record
- CVE
- CVE-2020-36312
- Published
- Apr 6, 2021
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-401, T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Apr 6, 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.
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