Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1402245 - (CVE-2016-9845) CVE-2016-9845 Qemu: display: virtio-gpu-3d: information leakage in virgl_cmd_get_capset_info
CVE-2016-9845 Qemu: display: virtio-gpu-3d: information leakage in virgl_cmd_...
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=20161101,reported=2...
: Security
Depends On: 1402247
Blocks: 1395985
  Show dependency treegraph
 
Reported: 2016-12-07 01:34 EST by Prasad J Pandit
Modified: 2018-07-18 11:07 EDT (History)
36 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 2016-12-07 01:34:52 EST
Quick Emulator(Qemu) built with the Virtio GPU Device emulator support is
vulnerable to an information leakage issue. It could occur while processing
'VIRTIO_GPU_CMD_GET_CAPSET_INFO' command.

A guest user/process could use this flaw to leak contents of the host memory
bytes.

Upstream patch:
---------------
  -> https://lists.nongnu.org/archive/html/qemu-devel/2016-11/msg00019.html

Reference:
----------
  -> http://www.openwall.com/lists/oss-security/2016/12/05/22
Comment 1 Prasad J Pandit 2016-12-07 01:42:13 EST
Created qemu tracking bugs for this issue:

Affects: fedora-all [bug 1402247]
Comment 3 Cole Robinson 2017-01-16 13:50:08 EST
commit 42a8dadc74f8982fc269e54e3c5627b54d9f83d8
Author: Li Qiang <liqiang6-s@360.cn>
Date:   Tue Nov 1 02:53:11 2016 -0700

    virtio-gpu: fix information leak in getting capset info dispatch

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