| Max CVSS | 6.1 | Min CVSS | 1.9 | Total Count | 2 |
| ID | CVSS | Summary | Last (major) update | Published | |
| CVE-2013-1920 | 4.4 |
Xen 4.2.x, 4.1.x, and earlier, when the hypervisor is running "under memory pressure" and the Xen Security Module (XSM) is enabled, uses the wrong ordering of operations when extending the per-domain event channel tracking table, which causes a use-a
|
29-08-2017 - 01:33 | 12-04-2013 - 22:55 | |
| CVE-2013-0153 | 4.7 |
The AMD IOMMU support in Xen 4.2.x, 4.1.x, 3.3, and other versions, when using AMD-Vi for PCI passthrough, uses the same interrupt remapping table for the host and all guests, which allows guests to cause a denial of service by injecting an interrupt
|
29-08-2017 - 01:32 | 14-02-2013 - 22:55 | |
| CVE-2013-1919 | 4.7 |
Xen 4.2.x and 4.1.x does not properly restrict access to IRQs, which allows local stub domain clients to gain access to IRQs and cause a denial of service via vectors related to "passed-through IRQs or PCI devices."
|
19-04-2014 - 04:34 | 13-05-2013 - 23:55 | |
| CVE-2013-1917 | 1.9 |
Xen 3.1 through 4.x, when running 64-bit hosts on Intel CPUs, does not clear the NT flag when using an IRET after a SYSENTER instruction, which allows PV guest users to cause a denial of service (hypervisor crash) by triggering a #GP fault, which is
|
19-04-2014 - 04:34 | 13-05-2013 - 23:55 | |
| CVE-2012-5634 | 6.1 |
Xen 4.2.x, 4.1.x, and 4.0, when using Intel VT-d for PCI passthrough, does not properly configure VT-d when supporting a device that is behind a legacy PCI Bridge, which allows local guests to cause a denial of service to other guests by injecting an
|
19-04-2014 - 04:28 | 14-02-2013 - 22:55 |