CVE-2019-19583: High severity xen xapi vulnerability
An issue was discovered in Xen through 4.12.x allowing x86 HVM/PVH guest OS users to cause a denial of service (guest OS crash) because VMX VMEntry checks mishandle a certain case. Please see XSA-260 for background on the MovSS shadow. Please see XSA-156 for background on the need for #DB interception. The VMX VMEntry checks do not like the exact combination of state which occurs when #DB in intercepted, Single Stepping is active, and blocked by STI/MovSS is active, despite this being a legitimate state to be in. The resulting VMEntry failure is fatal to the guest. HVM/PVH guest userspace code may be able to crash the guest, resulting in a guest Denial of Service. All versions of Xen are affected. Only systems supporting VMX hardware virtual extensions (Intel, Cyrix, or Zhaoxin CPUs) are affected. Arm and AMD systems are unaffected. Only HVM/PVH guests are affected. PV guests cannot leverage the vulnerability.
Affected Software
Remediation
Patch Available
Event History
Frequently Asked Questions
What is the severity of CVE-2019-19583?
CVE-2019-19583 has a severity rating that can lead to denial of service due to a guest OS crash.
Which versions of Xen are affected by CVE-2019-19583?
CVE-2019-19583 affects Xen versions from 4.8.0 to 4.12.1 and specific versions in the 4.11.x, 4.14.x, and 4.17.x series.
How do I fix CVE-2019-19583?
To fix CVE-2019-19583, you should upgrade to a patched version of Xen that is beyond 4.12.1.
What issue does CVE-2019-19583 address in Xen?
CVE-2019-19583 addresses mishandled VMX VMEntry checks that can cause a denial of service.
What environments are impacted by CVE-2019-19583?
CVE-2019-19583 impacts environments running guest OSes on Xen hypervisors, specifically on certain Linux distributions like Debian and Fedora.