CVE-2014-1666: High severity XEN Xen vulnerability
The dophysdevop function in Xen 4.1.5, 4.1.6.1, 4.2.2 through 4.2.3, and 4.3.x does not properly restrict access to the (1) PHYSDEVOPpreparemsix and (2) PHYSDEVOPreleasemsix operations, which allows local PV guests to cause a denial of service (host or guest malfunction) or possibly gain privileges via unspecified vectors.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
Xento a version that resolves this vulnerability.Fixed in 4.1.5 - Upgrade
Upgrade
Xento a version that resolves this vulnerability.Fixed in 4.1.6.1 - Upgrade
Upgrade
Xento a version that resolves this vulnerability.Fixed in 4.2.2 - Upgrade
Upgrade
Xento a version that resolves this vulnerability.Fixed in 4.2.3 - Compensating control
Mitigate by restricting access to the Xen physdev operations PHYSDEVOP_prepare_msix and PHYSDEVOP_release_msix (e.g., ensure only authorized/local-privileged PV guests can invoke these physdev MSIX operations).
Event History
Frequently Asked Questions
What is the severity of CVE-2014-1666?
CVE-2014-1666 is classified as a medium to high severity vulnerability due to the potential for denial of service and unauthorized privilege escalation.
How do I fix CVE-2014-1666?
To fix CVE-2014-1666, you should update Xen to version 4.4.0 or later, which includes patches addressing this vulnerability.
Which versions of Xen are affected by CVE-2014-1666?
CVE-2014-1666 affects Xen versions 4.1.5, 4.1.6.1, 4.2.2, 4.2.3, and 4.3.x.
What are the potential impacts of CVE-2014-1666 if left unpatched?
If left unpatched, CVE-2014-1666 can lead to host or guest malfunctions and may allow local guests to gain elevated privileges.
Who is at risk from CVE-2014-1666?
Local PV guests running on affected Xen versions are at risk due to improper access controls in the do_physdev_op function.