Memory disclosure via lost deferred TLB flushes
Published Jan 31, 2020 · Updated Sep 30, 2024
Information disclosure in Linux KVM allows local users in a guest kernel to read memory belonging to another process in that guest. A race can let KVM clear or acknowledge a deferred PV-TLB flush while a new request is pending, leaving a stale vCPU address translation usable. Reachability requires PV TLB exposure to a guest running Linux 4.16 or later on a host running Linux 4.10 or later; the feature is not enabled by default.
Summary
What happened
Information disclosure in Linux KVM allows local users in a guest kernel to read memory belonging to another process in that guest. A race can let KVM clear or acknowledge a deferred PV-TLB flush while a new request is pending, leaving a stale vCPU address translation usable. Reachability requires PV TLB exposure to a guest running Linux 4.16 or later on a host running Linux 4.10 or later; the feature is not enabled by default.
The record
- CVE
- CVE-2019-3016
- Published
- Jan 31, 2020
- Updated
- Sep 30, 2024
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- CWE-362, CWE-200
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jan 31, 2020CVE publishedPublication date reported by the CVE source.
- Sep 30, 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=4.10 to 5.6
What conditions does exploitation require?
What is affected?
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