Bug 851193 (CVE-2012-3498)

Summary:	CVE-2012-3498 kernel: xen: PHYSDEVOP_map_pirq index vulnerability
Product:	[Other] Security Response	Reporter:	Petr Matousek <pmatouse>
Component:	vulnerability	Assignee:	Red Hat Product Security <security-response-team>
Status:	CLOSED NOTABUG	QA Contact:
Severity:	medium	Docs Contact:
Priority:	medium
Version:	unspecified	CC:	drjones, lersek, pbonzini, security-response-team, tburke
Target Milestone:	---	Keywords:	Security
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-06-10 10:59:13 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	854593
Bug Blocks:	851204

Description Petr Matousek 2012-08-23 13:21:49 UTC

PHYSDEVOP_map_pirq with MAP_PIRQ_TYPE_GSI does not range check map->index.

A malicious HVM guest kernel can crash the host.  It might also be able to read hypervisor or guest memory.

All Xen systems running HVM guests are vulnerable.  PV guests are not vulnerable.

Acknowledgements:

Red Hat would like to thank the Xen project for reporting this issue. Upstream acknowledges Matthew Daley as the original reporter.

Comment 3 Petr Matousek 2012-08-23 13:29:59 UTC

Statement:

Not vulnerable.

This issue did not affect the versions of the kernel-xen package as shipped with Red Hat Enterprise Linux 5.

This issue did not affect Red Hat Enterprise Linux 6 and Red Hat Enterprise MRG as we did not have support for Xen hypervisor.

Comment 4 Petr Matousek 2012-09-05 11:54:09 UTC

Now public via:

http://seclists.org/oss-sec/2012/q3/380

Comment 5 Petr Matousek 2012-09-05 11:55:11 UTC

Created xen tracking bugs for this issue

Affects: fedora-all [bug 854593]

Comment 6 Fedora Update System 2012-09-17 18:00:19 UTC

xen-4.1.3-2.fc16 has been pushed to the Fedora 16 stable repository.  If problems still persist, please make note of it in this bug report.