An issue was discovered in Xen through 4.14.x. There are missing memory barriers when accessing/allocating an event channel. Event channels control structures can be accessed lockless as long as the port is considered to be valid. Such a sequence is missing an appropriate memory barrier (e.g., smp_*mb()) to prevent both the compiler and CPU from re-ordering access. A malicious guest may be able to cause a hypervisor crash resulting in a Denial of Service (DoS). Information leak and privilege escalation cannot be excluded. Systems running all versions of Xen are affected. Whether a system is vulnerable will depend on the CPU and compiler used to build Xen. For all systems, the presence and the scope of the vulnerability depend on the precise re-ordering performed by the compiler used to build Xen. We have not been able to survey compilers; consequently we cannot say which compiler(s) might produce vulnerable code (with which code generation options). GCC documentation clearly suggests that re-ordering is possible. Arm systems will also be vulnerable if the CPU is able to re-order memory access. Please consult your CPU vendor. x86 systems are only vulnerable if a compiler performs re-ordering.
{ "availability": "No subscription required", "ubuntu_priority": "medium", "binaries": [ { "xen-doc": "4.11.3+24-g14b62ab3e5-1ubuntu2.3", "libxengnttab1": "4.11.3+24-g14b62ab3e5-1ubuntu2.3", "libxendevicemodel1-dbgsym": "4.11.3+24-g14b62ab3e5-1ubuntu2.3", "xen-hypervisor-4.11-armhf": "4.11.3+24-g14b62ab3e5-1ubuntu2.3", "xen-hypervisor-4.9-armhf": "4.11.3+24-g14b62ab3e5-1ubuntu2.3", "libxenevtchn1-dbgsym": "4.11.3+24-g14b62ab3e5-1ubuntu2.3", "libxentoolcore1-dbgsym": "4.11.3+24-g14b62ab3e5-1ubuntu2.3", "libxentoollog1-dbgsym": "4.11.3+24-g14b62ab3e5-1ubuntu2.3", "xen-hypervisor-common": "4.11.3+24-g14b62ab3e5-1ubuntu2.3", "xen-hypervisor-4.9-arm64": "4.11.3+24-g14b62ab3e5-1ubuntu2.3", "libxenforeignmemory1": "4.11.3+24-g14b62ab3e5-1ubuntu2.3", "libxencall1": "4.11.3+24-g14b62ab3e5-1ubuntu2.3", "xen-utils-common-dbgsym": "4.11.3+24-g14b62ab3e5-1ubuntu2.3", "xen-utils-4.11-dbgsym": "4.11.3+24-g14b62ab3e5-1ubuntu2.3", "libxenmisc4.11-dbgsym": "4.11.3+24-g14b62ab3e5-1ubuntu2.3", "xen-system-arm64": "4.11.3+24-g14b62ab3e5-1ubuntu2.3", "xenstore-utils-dbgsym": "4.11.3+24-g14b62ab3e5-1ubuntu2.3", "libxenstore3.0": "4.11.3+24-g14b62ab3e5-1ubuntu2.3", "xen-hypervisor-4.11-arm64": "4.11.3+24-g14b62ab3e5-1ubuntu2.3", "libxengnttab1-dbgsym": "4.11.3+24-g14b62ab3e5-1ubuntu2.3", "libxenstore3.0-dbgsym": "4.11.3+24-g14b62ab3e5-1ubuntu2.3", "xen-hypervisor-4.9-amd64": "4.11.3+24-g14b62ab3e5-1ubuntu2.3", "libxenforeignmemory1-dbgsym": "4.11.3+24-g14b62ab3e5-1ubuntu2.3", "libxendevicemodel1": "4.11.3+24-g14b62ab3e5-1ubuntu2.3", "libxen-dev": "4.11.3+24-g14b62ab3e5-1ubuntu2.3", "xen-system-amd64": "4.11.3+24-g14b62ab3e5-1ubuntu2.3", "libxentoolcore1": "4.11.3+24-g14b62ab3e5-1ubuntu2.3", "libxencall1-dbgsym": "4.11.3+24-g14b62ab3e5-1ubuntu2.3", "xenstore-utils": "4.11.3+24-g14b62ab3e5-1ubuntu2.3", "libxenevtchn1": "4.11.3+24-g14b62ab3e5-1ubuntu2.3", "xen-utils-common": "4.11.3+24-g14b62ab3e5-1ubuntu2.3", "xen-system-armhf": "4.11.3+24-g14b62ab3e5-1ubuntu2.3", "libxentoollog1": "4.11.3+24-g14b62ab3e5-1ubuntu2.3", "xen-hypervisor-4.11-amd64": "4.11.3+24-g14b62ab3e5-1ubuntu2.3", "xen-utils-4.11": "4.11.3+24-g14b62ab3e5-1ubuntu2.3", "libxenmisc4.11": "4.11.3+24-g14b62ab3e5-1ubuntu2.3" } ] }