p PatchFirst

CVE-2019-19583

CVE-2019-19583

This page contains facts from public vulnerability sources. Check the original advisory before updating.

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.

CVSS 7.5 · High · EPSS 2.4% · Fix available

Published
Updated

Stack: system

Affected products and versions

  • n/a

    Versions
    • n/a: Affected

    No fix published

  • xen Debian:12

    Affected ranges
    • ECOSYSTEM: < 4.11.3+24-g14b62ab3e5-1

    Update to 4.11.3+24-g14b62ab3e5-1

  • xen Debian:13

    Affected ranges
    • ECOSYSTEM: < 4.11.3+24-g14b62ab3e5-1

    Update to 4.11.3+24-g14b62ab3e5-1

  • xen Debian:14

    Affected ranges
    • ECOSYSTEM: < 4.11.3+24-g14b62ab3e5-1

    Update to 4.11.3+24-g14b62ab3e5-1

  • xen Ubuntu:16.04:LTS

    Versions
    • 4.5.1-0ubuntu1
    • 4.5.1-0ubuntu2
    • 4.6.0-1ubuntu1
    • 4.6.0-1ubuntu2
    • 4.6.0-1ubuntu4
    • 4.6.0-1ubuntu4.1
    • 4.6.0-1ubuntu4.2
    • 4.6.0-1ubuntu4.3
    • 4.6.5-0ubuntu1
    • 4.6.5-0ubuntu1.1
    • 4.6.5-0ubuntu1.2
    • 4.6.5-0ubuntu1.4
    Affected ranges
    • ECOSYSTEM: (−∞, +∞)

    No fix published

  • xen Ubuntu:18.04:LTS

    Versions
    • 4.9.0-0ubuntu3
    • 4.9.0-0ubuntu4
    • 4.9.2-0ubuntu1
    Affected ranges
    • ECOSYSTEM: (−∞, +∞)

    No fix published

Original sources

Check your server →