An issue was discovered in xenoprof in Xen through 4.13.x, allowing guest OS users (with active profiling) to obtain sensitive information about other guests, cause a denial of service, or possibly gain privileges. For guests for which active profiling was enabled by the administrator, the xenoprof code uses the standard Xen shared ring structure. Unfortunately, this code did not treat the guest as a potential adversary: it trusts the guest not to modify buffer size information or modify head / tail pointers in unexpected ways. This can crash the host (DoS). Privilege escalation cannot be ruled out.
The product does not initialize a critical resource.
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Xen | Xen | * | 4.13.0 (including) |
| Xen | Xen | 4.13.0-rc1 (including) | 4.13.0-rc1 (including) |
| Xen | Xen | 4.13.0-rc2 (including) | 4.13.0-rc2 (including) |
| Xen | Ubuntu | bionic | * |
| Xen | Ubuntu | eoan | * |
| Xen | Ubuntu | esm-infra/bionic | * |
| Xen | Ubuntu | esm-infra/xenial | * |
| Xen | Ubuntu | focal | * |
| Xen | Ubuntu | groovy | * |
| Xen | Ubuntu | hirsute | * |
| Xen | Ubuntu | impish | * |
| Xen | Ubuntu | trusty | * |
| Xen | Ubuntu | xenial | * |