CVE-2017-10916 json
The vCPU context-switch implementation in Xen through 4.8.x improperly interacts with the Memory Protection Extensions (MPX) and Protection…
published 9y ago modified 4mo ago also EUVD-2017-2554
- cvss
- 7.5
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.3%
- EPSS 1.3% chance of exploitation in 30 days, percentile 71%
- public exploits
- 0
- none known
Summary
The vCPU context-switch implementation in Xen through 4.8.x improperly interacts with the Memory Protection Extensions (MPX) and Protection Key (PKU) features, which makes it easier for guest OS users to defeat ASLR and other protection mechanisms, aka XSA-220.
Patch / fix
- xen Debian 14, Debian 13, Debian 12 4.8.1-1+deb9u3
debian advisories DEBIAN-CVE-2017-10916
- xen Ubuntu 16.04 LTS 4.6.5-0ubuntu1.2
ubuntu advisories UBUNTU-CVE-2017-10916
Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
- xen SLES for SAP 12 SP1, SLES 12 SP1-LTSS, OpenStack Cloud 6 4.5.5_12-22.18.1
suse advisories SUSE-SU-2017:1812-1
- xen Alpine 3.24, Alpine 3.23, Alpine 3.22 +15 more 4.9.0-r0
- xen Alpine 3.4, Alpine 3.3 4.6.6-r0
- xen Alpine 3.5 4.7.3-r0
- xen Alpine 3.6 4.8.2-r0
alpine advisories ALPINE-CVE-2017-10916
Alpine secdb © Alpine Linux, from https://secdb.alpinelinux.org via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
Is CVE-2017-10916 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerVendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2017-10916 updated cvss 8.0
xen: x86: PKRU and BND* leakage between vCPU-s (XSA-220)
-
Red Hat Enterprise Linux 5 xennot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
1.35% chance of exploitation in the next 30 days, higher than 71% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 7.5 | CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N |
| NVD | 2.0 | 5.0 | AV:N/AC:L/Au:N/C:P/I:N/A:N |
Classification
- Weakness
-
- CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
References
-
security.gentoo.org
/glsa/201708-03
vendor-advisory
-
debian.org
/security/2017/dsa-3969
vendor-advisory
-
xenbits.xen.org
/xsa/advisory-220.html
mailing-list, mitigation, vendor-advisory
-
securitytracker.com
/id/1038730
vdb-entry
-
securityfocus.com
/bid/99167
vdb-entry
Sources
- CVE List CVE-2017-10916
- NVD CVE-2017-10916
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.