Bug 1518657 (CVE-2017-17563, xsa249) - CVE-2017-17563 xsa249 xen: broken x86 shadow mode refcount overflow check (XSA-249)
Summary: CVE-2017-17563 xsa249 xen: broken x86 shadow mode refcount overflow check (XS...
Alias: CVE-2017-17563, xsa249
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
Depends On: 1525018
TreeView+ depends on / blocked
Reported: 2017-11-29 12:26 UTC by Adam Mariš
Modified: 2021-02-17 01:11 UTC (History)
13 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2019-06-08 03:32:26 UTC

Attachments (Terms of Use)

Description Adam Mariš 2017-11-29 12:26:14 UTC

Pages being used to run x86 guests in shadow mode are reference counted
to track their uses.  Unfortunately the overflow check when trying to
obtain a new reference used a mask one bit wider than the reference
count actually is, rendering the entire check ineffective.


A malicious or buggy guest may cause a hypervisor crash, resulting in
a Denial of Service (DoS) affecting the entire host, or cause hypervisor
memory corruption.  We cannot rule out a guest being able to escalate
its privilege.


Xen versions 4.1 and later are affected.  Xen versions 4.0 and earlier
are not affected.

x86 systems are vulnerable.  ARM systems are not vulnerable.

Only guests run in shadow mode can exploit the vulnerability.

PV guests typically only run in shadow mode during live migration, as
well as for features like VM snapshot.

Note that save / restore does *not* use shadow mode, and so does not
expose this vulnerability.  Some downstreams also include a "non-live
migration" feature, which also does not use shadow mode (and thus does
not expose this vulnerability).

HVM guests run in shadow mode on hardware without HAP support, or when
HAP is disabled (globally or in the VM configuration file).  Live
migration does not affect an HVM guest's use of shadow mode.


For HVM guest explicitly configured to use shadow paging (e.g. via the
`hap=0' xl domain configuration file parameter), changing to HAP (e.g.
by setting `hap=1') will avoid exposing the vulnerability to those
guests.  HAP is the default (in upstream Xen), where the hardware
supports it; so this mitigation is only applicable if HAP has been
disabled by configuration.

For PV guests, avoiding their live migration avoids the vulnerability.

External References:


Comment 2 Adam Mariš 2017-12-12 13:13:54 UTC

Name: the Xen project
Upstream: Jan Beulich (SUSE)

Comment 3 Adam Mariš 2017-12-12 13:16:45 UTC
Created xen tracking bugs for this issue:

Affects: fedora-all [bug 1525018]

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