An issue was discovered in Xen through 4.9.x allowing x86 PV guest OS users to execute arbitrary code on the host OS because of a race condition that can cause a stale TLB entry.
The product contains a concurrent code sequence that requires temporary, exclusive access to a shared resource, but a timing window exists in which the shared resource can be modified by another code sequence operating concurrently.
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Xen | Xen | 4.9.0 (including) | 4.9.0 (including) |
| Xen | Ubuntu | artful | * |
| Xen | Ubuntu | bionic | * |
| Xen | Ubuntu | esm-infra/bionic | * |
| Xen | Ubuntu | esm-infra/xenial | * |
| Xen | Ubuntu | trusty | * |
| Xen | Ubuntu | upstream | * |
| Xen | Ubuntu | xenial | * |
| Xen | Ubuntu | zesty | * |
A race condition occurs within concurrent environments, and it is effectively a property of a code sequence. Depending on the context, a code sequence may be in the form of a function call, a small number of instructions, a series of program invocations, etc. A race condition violates these properties, which are closely related:
A race condition exists when an “interfering code sequence” can still access the shared resource, violating exclusivity. The interfering code sequence could be “trusted” or “untrusted.” A trusted interfering code sequence occurs within the product; it cannot be modified by the attacker, and it can only be invoked indirectly. An untrusted interfering code sequence can be authored directly by the attacker, and typically it is external to the vulnerable product.