Bug 1285350 (xsa163) - xen: Virtual Performance Measurement Unit feature is unsupported
Summary: xen: Virtual Performance Measurement Unit feature is unsupported
Keywords:
Status: CLOSED NOTABUG
Alias: xsa163
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
URL:
Whiteboard: impact=moderate,public=20151125,repor...
Depends On: 1285351
Blocks: 1284949
TreeView+ depends on / blocked
 
Reported: 2015-11-25 12:45 UTC by Adam Mariš
Modified: 2019-06-08 20:51 UTC (History)
37 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
The Virtual Performance Measurement Unit feature has been documented as unsupported on Intel CPUs. Further issues have been found or are suspected which would also (or exclusively) affect AMD CPUs. Use of the feature may have unknown effects, ranging from information leaks through Denial of Service to privilege escalation.
Clone Of:
Environment:
Last Closed: 2017-10-19 12:42:02 UTC


Attachments (Terms of Use)

Description Adam Mariš 2015-11-25 12:45:53 UTC
The Virtual Performance Measurement Unit feature has been documented as unsupported on Intel CPUs. Further issues have been found or are suspected which would also (or exclusively) affect AMD CPUs. Use of the feature may have unknown effects, ranging from information leaks through Denial of Service to privilege escalation.

Only systems which enable the VPMU feature are affected. That is, only systems with a `vpmu' setting on the hypervisor command line. Xen versions from 3.3 onwards are affected. Only x86 systems are affected. ARM systems do not currently implement vPMU and are therefore currently unaffected. In Xen versions prior to 4.6 only HVM guests can take advantage of this unsupported functionality. In Xen versions from 4.6 onwards all guest kinds can use this unsupported functionality. Not enabling vPMU support (by omitting the "vpmu" hypervisor command line option) will avoid using and exposing the unsupported functionality.

Comment 1 Adam Mariš 2015-11-25 12:46:24 UTC
Created xen tracking bugs for this issue:

Affects: fedora-all [bug 1285351]

Comment 2 Martin Prpič 2015-12-08 12:41:23 UTC
External References:

http://xenbits.xen.org/xsa/advisory-163.html

Comment 3 Martin Prpič 2015-12-08 12:45:09 UTC
Acknowledgments:

Red Hat would like to thank the Xen project for reporting this issue.

Comment 4 Fedora Update System 2015-12-17 07:26:34 UTC
xen-4.5.2-5.fc23 has been pushed to the Fedora 23 stable repository. If problems still persist, please make note of it in this bug report.

Comment 5 Fedora Update System 2015-12-20 00:22:44 UTC
xen-4.5.2-5.fc22 has been pushed to the Fedora 22 stable repository. If problems still persist, please make note of it in this bug report.

Comment 6 Wade Mealing 2017-10-19 12:17:26 UTC
Statement:

This issue does not affect the Linux kernel packages as shipped with Red Hat
Enterprise Linux 5,6,7, MRG-2 and realtime.

The code that enables VPMU as a valid instructions are not included in the
initial version of xen that ships with Red Hat Enterprise Linux 5.

Comment 10 Wade Mealing 2017-10-19 12:35:29 UTC
Mitigation:

At this time this flaw only affects systems with the hypervisor booted with the vpmu parameter, which is not supported by the version shipping with Red Hat Enterprise Linux 5.


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