Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1452597 - (CVE-2017-9060) CVE-2017-9060 Qemu: virtio-gpu: host memory leakage in Virtio GPU device
CVE-2017-9060 Qemu: virtio-gpu: host memory leakage in Virtio GPU device
Status: NEW
Product: Security Response
Classification: Other
Component: vulnerability (Show other bugs)
unspecified
All Linux
low Severity low
: ---
: ---
Assigned To: Red Hat Product Security
impact=low,public=20170122,reported=2...
: Security
Depends On: 1452598
Blocks: 1377134
  Show dependency treegraph
 
Reported: 2017-05-19 06:02 EDT by Prasad J Pandit
Modified: 2018-07-18 11:22 EDT (History)
38 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed:
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Prasad J Pandit 2017-05-19 06:02:55 EDT
Quick Emulator(Qemu) built with the Virtio GPU Device emulator support is
vulnerable to a memory leakage issue. It could occur while processing
'VIRTIO_GPU_CMD_SET_SCANOUT:' command.

A guest user/process could use this flaw to leak host memory resulting in Dos.

Upstream patch:
---------------
  -> http://git.qemu.org/?p=qemu.git;a=commitdiff;h=dd248ed7e204ee8a1873914e02b8b526e8f1b80d

Reference:
----------
  -> http://www.openwall.com/lists/oss-security/2017/05/19/1
Comment 1 Prasad J Pandit 2017-05-19 06:03:37 EDT
Acknowledgments:

Name: Li Qiang (Qihoo 360 Gear Team)
Comment 2 Prasad J Pandit 2017-05-19 06:06:04 EDT
Created qemu tracking bugs for this issue:

Affects: fedora-all [bug 1452598]
Comment 3 Fedora Update System 2017-07-25 17:26:26 EDT
qemu-2.7.1-7.fc25 has been pushed to the Fedora 25 stable repository. If problems still persist, please make note of it in this bug report.

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