Race condition in HVMOP_track_dirty_vram in Xen 4.0.0 through 4.4.x does not ensure possession of the guarding lock for dirty video RAM tracking, which allows certain local guest domains to cause a denial of service via unspecified vectors.
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.
Link | Tags |
---|---|
http://secunia.com/advisories/61501 | third party advisory |
http://lists.opensuse.org/opensuse-security-announce/2014-10/msg00003.html | third party advisory vendor advisory |
http://lists.fedoraproject.org/pipermail/package-announce/2014-October/140483.html | third party advisory vendor advisory |
http://lists.opensuse.org/opensuse-security-announce/2014-10/msg00002.html | third party advisory vendor advisory |
http://lists.fedoraproject.org/pipermail/package-announce/2014-October/140418.html | third party advisory vendor advisory |
http://www.debian.org/security/2014/dsa-3041 | third party advisory vendor advisory |
http://xenbits.xen.org/xsa/advisory-104.html | patch vendor advisory |
http://secunia.com/advisories/61890 | third party advisory |
http://security.gentoo.org/glsa/glsa-201412-42.xml | vendor advisory |
http://www.securitytracker.com/id/1030887 | vdb entry third party advisory |