Bug 956309 (CVE-2013-1952) - CVE-2013-1952 kernel: xen: VT-d interrupt remapping source validation flaw for bridges
Summary: CVE-2013-1952 kernel: xen: VT-d interrupt remapping source validation flaw fo...
Keywords:
Status: CLOSED NOTABUG
Alias: CVE-2013-1952
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:
Depends On: 958919
Blocks: 953634
TreeView+ depends on / blocked
 
Reported: 2013-04-24 16:02 UTC by Petr Matousek
Modified: 2023-05-11 22:45 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-05-02 16:37:56 UTC
Embargoed:


Attachments (Terms of Use)

Description Petr Matousek 2013-04-24 16:02:18 UTC
Interrupt remapping table entries for MSI interrupts set up by bridge devices did not get any source validation set up on them, allowing misbehaving or malicious guests to inject interrupts into the domain owning the bridges.

In a typical Xen system bridge devices are owned by domain 0, leaving it vulnerable to such an attack. Such a DoS is likely to have an impact on other guests running in the system.

A malicious domain, given access to a device which bus mastering capable, can mount a denial of service attack affecting the whole system.

Acknowledgements:

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

Comment 3 Petr Matousek 2013-04-24 16:05:09 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 2013-05-02 16:36:34 UTC
Now public via http://seclists.org/oss-sec/2013/q2/260.

Comment 5 Petr Matousek 2013-05-02 16:37:35 UTC
Created xen tracking bugs for this issue

Affects: fedora-all [bug 958919]


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