Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 609206 - <app-emulation/qemu-2.8.0-r3: display: cirrus_bitblt_cputovideo does not check if memory region is safe (CVE-2017-2620)
Summary: <app-emulation/qemu-2.8.0-r3: display: cirrus_bitblt_cputovideo does not chec...
Alias: None
Product: Gentoo Security
Classification: Unclassified
Component: Vulnerabilities (show other bugs)
Hardware: All Linux
: Normal major (vote)
Assignee: Gentoo Security
Whiteboard: B1 [glsa cve]
Depends on:
Blocks: CVE-2017-2620 CVE-2017-5973 CVE-2017-2630 CVE-2017-5987 CVE-2017-6058
  Show dependency tree
Reported: 2017-02-13 02:32 UTC by Thomas Deutschmann (RETIRED)
Modified: 2017-04-10 21:26 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---
stable-bot: sanity-check+


Note You need to log in before you can comment on or make changes to this bug.
Description Thomas Deutschmann (RETIRED) gentoo-dev 2017-02-13 02:32:43 UTC

In CIRRUS_BLTMODE_MEMSYSSRC mode the bitblit copy routine
cirrus_bitblt_cputovideo fails to check wethehr the specified memory
region is safe.


A malicious guest administrator can cause an out of bounds memory
write, very likely exploitable as a privilege escalation.


Versions of qemu shipped with all Xen versions are vulnerable.

Xen systems running on x86 with HVM guests, with the qemu process
running in dom0 are vulnerable.

Only guests provided with the "cirrus" emulated video card can exploit
the vulnerability.  The non-default "stdvga" emulated video card is
not vulnerable.  (With xl the emulated video card is controlled by the
"stdvga=" and "vga=" domain configuration options.)

ARM systems are not vulnerable.  Systems using only PV guests are not

For VMs whose qemu process is running in a stub domain, a successful
attacker will only gain the privileges of that stubdom, which should
be only over the guest itself.

Both upstream-based versions of qemu (device_model_version="qemu-xen")
and `traditional' qemu (device_model_version="qemu-xen-traditional")
are vulnerable.


Running only PV guests will avoid the issue.

Running HVM guests with the device model in a stubdomain will mitigate
the issue.

Changing the video card emulation to stdvga (stdvga=1, vga="stdvga",
in the xl domain configuration) will avoid the vulnerability.


Deployment of the patches described above (or others which are
substantially similar) is permitted during the embargo, even on
public-facing systems with untrusted guest users and administrators.

However, deployment of the "stdvga" mitigation (changing the video
card emulation to stdvga) is NOT permitted (except where all the
affected systems and VMs are administered and used only by
organisations which are members of the Xen Project Security Issues
Predisclosure List).  Specifically, deployment on public cloud systems
is NOT permitted.  This is because this produces a guest-visible
change which will indicate which component contains the vulnerability.

Additionally, distribution of updated software is prohibited (except
to other members of the predisclosure list).

Predisclosure list members who wish to deploy significantly different
patches and/or mitigations, please contact the Xen Project Security

(Note: this during-embargo deployment notice is retained in
post-embargo publicly released Xen Project advisories, even though it
is then no longer applicable.  This is to enable the community to have
oversight of the Xen Project Security Team's decisionmaking.)
Comment 1 Matthias Maier gentoo-dev 2017-02-13 05:18:14 UTC
I have pushed 2.8.0-r1 to the tree that contains the published upstream fix

  commit 62d4c6bd5263bb8413a06c80144fc678df6dfb64
  Author: Li Qiang <>
  Date:   Wed Feb 1 09:35:01 2017 +0100

      cirrus: fix oob access issue (CVE-2017-2615)

This specific patch is handled in bug #608034, stabilization on #608728
Comment 2 Matthias Maier gentoo-dev 2017-02-13 05:26:41 UTC
*ugh* I mixed up the CVEs.

Please disregard my previous comment.
Comment 3 Matthias Maier gentoo-dev 2017-02-21 03:28:37 UTC
Patchset is prepared. I will push the patch for this bug (and the other open CVE patches) at precisely 12:00pm.
Comment 4 Thomas Deutschmann (RETIRED) gentoo-dev 2017-02-21 12:04:02 UTC
@ Maintainer(s): Please proceed!
Comment 5 Matthias Maier gentoo-dev 2017-02-21 12:05:40 UTC
commit cc47fc6cf1fef191ebb6c19d4b8bba9a12294024
Author: Matthias Maier <>
Date:   Mon Feb 20 21:27:40 2017 -0600

    app-emulation/qemu: security fixes, notably CVE-2017-2620, bug #609206
    This commit applies a number of patches fixing
      CVE-2017-2620 #609206
      CVE-2017-2630 #609396
      CVE-2017-5973 #609334
      CVE-2017-5987 #609398
      CVE-2017-6058 #609638
    Package-Manager: Portage-2.3.3, Repoman-2.3.1
Comment 6 Matthias Maier gentoo-dev 2017-02-21 12:09:20 UTC
Arches, please stabilize

Target-keywords: "amd64 x86"
Comment 7 Agostino Sarubbo gentoo-dev 2017-02-22 15:08:29 UTC
amd64 stable
Comment 8 Agostino Sarubbo gentoo-dev 2017-02-22 16:10:44 UTC
x86 stable.

Maintainer(s), please cleanup.
Security, please add it to the existing request, or file a new one.
Comment 9 Matthias Maier gentoo-dev 2017-02-22 19:18:22 UTC
commit 6db0a37a742a067e1df7b6e82147f09289c0ebd1
Author: Matthias Maier <>
Date:   Wed Feb 22 13:16:26 2017 -0600

    app-emulation/qemu: remove vulnerable 2.8.0-r1, bug #609206
    Package-Manager: Portage-2.3.3, Repoman-2.3.1
Comment 10 Yury German Gentoo Infrastructure gentoo-dev 2017-03-28 03:28:58 UTC
Arches and Maintainer(s), Thank you for your work.

New GLSA Request filed.
Comment 11 GLSAMaker/CVETool Bot gentoo-dev 2017-04-10 21:26:31 UTC
This issue was resolved and addressed in
 GLSA 201704-01 at
by GLSA coordinator Kristian Fiskerstrand (K_F).