Menu

Star on GitHub · 3.2k

CVE-2019-3016

6.2 · MEDIUM

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.

Published Jan 31, 2020CWE-200EPSS 0.62%

Overview

CVE-2019-3016 is a medium-severity vulnerability. It was published on January 31, 2020 and has a CVSS 3.1 base score of 6.2 (MEDIUM).

This vulnerability has a CVSS 3.1 base score of 6.2, rated MEDIUM. It requires local or adjacent network access to exploit. No authentication or special privileges are required for exploitation.

Technical description

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.

Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

Frequently asked questions

What is CVE-2019-3016?

CVE-2019-3016 is a medium-severity vulnerability. It was published on January 31, 2020 and has a CVSS 3.1 base score of 6.2 (MEDIUM).

How severe is CVE-2019-3016?

This vulnerability has a CVSS 3.1 base score of 6.2, rated MEDIUM. It requires local or adjacent network access to exploit. No authentication or special privileges are required for exploitation.

How do I fix or remediate CVE-2019-3016?

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2019-3016?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2019-3016 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.

Related MEDIUM CVEs from 2019

View all