REDHAT-BUG-906032: Medium severity qemu vulnerability
A flaw was found in the way spice connection breakups were handled in the qemu-kvm qxl driver. Some of the qxl port i/o commands were waiting for the spice server to complete the actions, while the corresponding thread holds qemumutex mutex, potentially blocking other threads in the guest's qemu-kvm process. An user able to initiate spice connection to the guest could use this flaw to make guest temporarily unavailable or, in case kernel.softlockuppanic in the guest was set, crash the guest.
Upstream fixes: xf86-video-qxl commit http://cgit.freedesktop.org/xorg/driver/xf86-video-qxl/commit/?id=30b4b72cdbdf9f0e92a8d1c4e01779f60f15a741
which relies on qemu-kvm functionality introduced by commit http://git.kernel.org/?p=virt/kvm/qemu-kvm.git;a=commit;h=5ff4e36c
Affected Software
Event History
Frequently Asked Questions
What is the severity of REDHAT-BUG-906032?
The severity of REDHAT-BUG-906032 is categorized as medium due to the potential for blocking other threads.
How do I fix REDHAT-BUG-906032?
You can fix REDHAT-BUG-906032 by updating to the patched version of the qemu-kvm and xf86-video-qxl drivers.
Which software is affected by REDHAT-BUG-906032?
REDHAT-BUG-906032 affects the QEMU qemu-kvm and X.Org xf86-video-qxl drivers.
What are the implications of REDHAT-BUG-906032?
The implications of REDHAT-BUG-906032 include potential performance degradation due to thread blocking.
Is there a known workaround for REDHAT-BUG-906032?
There is no widely recommended workaround for REDHAT-BUG-906032; updating is advised.