Microsoft security update for CVE-2019-3016
🔗 CVE IDs covered (1)
📋 Microsoft's advisory
EchelonGraph does not copy Microsoft's advisory page: its FAQ and remediation text are not shown here. Read the advisory on https://msrc.microsoft.com/update-guide/vulnerability/CVE-2019-3016. This page also shows what EchelonGraph holds for CVE-2019-3016, with the description from its CVE record, which the CVE Numbering Authority that assigned the CVE wrote: for a CVE Microsoft assigned, often in the words of Microsoft's own advisory.
🎯 Affected products4
- azl3 kernel 6.6.29.1-4 on Azure Linux 3.0
- azl3 kernel 6.6.92.2-1 on Azure Linux 3.0
- cbl2 kernel 5.10.78.1-1 on CBL Mariner 2.0
- cm1 kernel 5.10.60.1-1 on CBL Mariner 1.0
✅ Updates Microsoft lists: 3 updates
3 rows: one per KB article or update, update type and fixed build. Their details are on Microsoft's advisory.
| KB article | Update | Fixed build |
|---|---|---|
| — | Security Update | - |
| — | Security Update | 5.10.78.1-1 |
| — | Security Update | 6.6.29.1-4 |
🧭 EchelonGraph on CVE-2019-3016
- EchelonGraph score
- 6.2 MEDIUM
- CISA KEV
- Not listed
- Fix status
- A fix is available — apply it.
Description from the CVE record (CVE.org), as published by its numbering authority
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.
Published by Oracle, the CVE Numbering Authority that assigned CVE-2019-3016, in its CVE record at CVE.org; reused under the CVE Program's Terms of Use (its licence and MITRE's copyright notice are in our Terms of Service).