Host denial of service via KVM initialization leak
Published May 9, 2020 · Updated Aug 4, 2024
Memory leak in the KVM SVM subsystem in Linux kernel before 5.6 allows local users to cause a crash during processor initialization. The svm_cpu_init function allocates a save-area page before allocating sd->sev_vmcbs, but the failure path returns without freeing the page. The finding is disputed because the one-time boot leak is negligible in size and cannot be triggered at will.
Summary
What happened
Memory leak in the KVM SVM subsystem in Linux kernel before 5.6 allows local users to cause a crash during processor initialization. The svm_cpu_init function allocates a save-area page before allocating sd->sev_vmcbs, but the failure path returns without freeing the page. The finding is disputed because the one-time boot leak is negligible in size and cannot be triggered at will.
The record
- CVE
- CVE-2020-12768
- Published
- May 9, 2020
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-401
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- May 9, 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