CVE-2019-3016
Reported by oracle · Published January 31, 2020
In a Linux KVM guest that has PV TLB enabled, a process in the guest kernel may be able to read memory locations from another process in the same guest. This problem is limit to the host running linux kernel 4.10 with a guest running linux kernel 4.16 or later. The problem mainly affects AMD processors but Intel CPUs cannot be ruled out.
Fixed versions
Upgrade to a fixed version or later. Language registries are listed first, then Linux distributions, then vendor products.
| Package | Ecosystem | Fixed in |
|---|---|---|
| kernel | Amazon Linux | 4.14.192-147.314.amzn2 |
| linux-qemu-melange | Chainguard | 6.18.16-r0 |
| linux-vmware-6.12 | Chainguard | 6.12.71-r0 |
| linux-gcp-5.3 | Ubuntu:18.04:LTS | 5.3.0-1014.15~18.04.1 |
| linux-gke-5.0 | Ubuntu:18.04:LTS | 5.0.0-1032.33 |
| linux-gcp | Ubuntu:18.04:LTS | 5.0.0-1033.34 |
| linux-oem-osp1 | Ubuntu:18.04:LTS | 5.0.0-1043.48 |
| linux-hwe | Ubuntu:18.04:LTS | 5.3.0-42.34~18.04.1 |
Risk scores
Affected products
| Vendor | Product | Versions |
|---|---|---|
| linux | linux_kernel | 4.10 to 5.6 |
| chainguard | linux-gcp-generic | * |
| chainguard | linux-aws-6.12 | * |
| amazon:2 | kernel | 0 |
| chainguard | linux-vmware-generic | * |
| chainguard | linux-qemu-rc | * |
| chainguard | linux | * |
| chainguard | linux-azure-6.12 | * |
| chainguard | linux-aws-6.18 | * |
| chainguard | linux-qemu-melange | 0 |
| chainguard | linux-vmware-6.12 | 0 |
| linux | linux_kernel | 4.10 |
| amazon:2 | kernel-devel | 0 |
| chainguard | linux-azure-6.18 | * |
| chainguard | linux-gcp-6.12 | * |
| amazon:2 | kernel-tools-devel | 0 |
| chainguard | linux-qemu-6.18 | 0 |
| amazon:2 | perf | 0 |
| chainguard | linux-qemu-6.12 | 0 |
| amazon:2 | python-perf | 0 |
…and 8 more
Timeline
- Jan 30, 2020 CVE Published
- Apr 14, 2021 EPSS Score (30 in total, the first dated here)
- Oct 24, 2025 CVE Updated
- Mar 6, 2026 Distribution Patch (7 in total, the first dated here)
- Mar 6, 2026 Security Advisory (8 in total, the first dated here)
- Sep 10, 2026 Coalition ESS Score
Query this with the API
The same record, from the CLI:
vulnetix vdb vuln CVE-2019-3016
vulnetix vdb fixes CVE-2019-3016
Or with curl, using the org id and key from your account page:
curl -s -H "Authorization: ApiKey ${VULNETIX_ORG_ID}:${VULNETIX_API_KEY}" \
"https://api.vdb.vulnetix.com/v2/vuln/CVE-2019-3016/fixes/registry"
The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart
References
- [oss-security] 20200130 CVE-2019-3016: information leak within a KVM guest mailing-listx_refsource_MLIST
- x_refsource_CONFIRM
- x_refsource_CONFIRM
- x_refsource_CONFIRM
- x_refsource_CONFIRM
- x_refsource_CONFIRM
- x_refsource_CONFIRM
- x_refsource_CONFIRM
- x_refsource_CONFIRM
- USN-4300-1 vendor-advisoryx_refsource_UBUNTU
- USN-4301-1 vendor-advisoryx_refsource_UBUNTU
- x_refsource_MISC
- DSA-4699 vendor-advisoryx_refsource_DEBIAN