Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1400438 - CVE-2017-2633 qemu-kvm coredump in vnc_refresh_server_surface [rhel-6.9.z]
CVE-2017-2633 qemu-kvm coredump in vnc_refresh_server_surface [rhel-6.9.z]
Status: CLOSED ERRATA
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: qemu-kvm (Show other bugs)
6.9
x86_64 Linux
unspecified Severity medium
: rc
: ---
Assigned To: Marc-Andre Lureau
Guo, Zhiyi
: Security, SecurityTracking
Depends On: 1437060
Blocks: CVE-2017-2633
  Show dependency treegraph
 
Reported: 2016-12-01 04:14 EST by Guo, Zhiyi
Modified: 2017-05-09 08:45 EDT (History)
15 users (show)

See Also:
Fixed In Version: qemu-kvm-0.12.1.2-2.503.el6_9.1
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2017-05-09 08:45:52 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2017:1206 normal SHIPPED_LIVE Important: qemu-kvm security update 2017-05-09 12:29:49 EDT

  None (edit)
Comment 18 Prasad J Pandit 2017-03-09 00:51:32 EST
Looks like this one won't make it into 6.9; Moving to 6.9.z.
Comment 21 Danilo Cesar de Paula 2017-03-27 09:34:26 EDT
Fix included in qemu-kvm-0.12.1.2-2.503.el6_9.1
Comment 23 Guo, Zhiyi 2017-03-30 01:55:11 EDT
Verified per comment https://bugzilla.redhat.com/show_bug.cgi?id=1425943#c5
Comment 25 errata-xmlrpc 2017-05-09 08:45:52 EDT
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2017:1206

Note You need to log in before you can comment on or make changes to this bug.