|Public release ||2014-09-23 12:00|
|Updated ||2014-09-24 10:29|
|Title ||Race condition in HVMOP_track_dirty_vram|
Filesadvisory-104.txt (signed advisory file)
-----BEGIN PGP SIGNED MESSAGE-----
Xen Security Advisory CVE-2014-7154 / XSA-104
Race condition in HVMOP_track_dirty_vram
UPDATES IN VERSION 3
This issue has been assigned CVE-2014-7154.
The routine controlling the setup of dirty video RAM tracking latches
the value of a pointer before taking the respective guarding lock, thus
making it possible for a stale pointer to be used by the time the lock
got acquired and the pointer gets dereferenced.
The hypercall providing access to the affected function is available to
the domain controlling HVM guests.
Malicious or buggy stub domain kernels or tool stacks otherwise living
outside of Domain0 can mount a denial of service attack which, if
successful, can affect the whole system.
Only domains controlling HVM guests can exploit this vulnerability.
(This includes domains providing hardware emulation services to HVM
Xen versions from 4.0.0 onwards are vulnerable.
This vulnerability is only applicable to Xen systems using stub
domains or other forms of disaggregation of control domains for HVM
There is no mitigation available for this issue.
(The security of a Xen system using stub domains is still better than
with a qemu-dm running as an unrestricted dom0 process. Therefore
users with these configurations should not switch to an unrestricted
This issue was discovered by Andrew Cooper at Citrix.
Applying the attached patch resolves this issue.
xsa104.patch xen-unstable, Xen 4.4.x, Xen 4.3.x, Xen 4.2.x
$ sha256sum xsa104*.patch
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
-----END PGP SIGNATURE-----
Xenproject.org Security Team