Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 1140280 - (CVE-2014-6268) CVE-2014-6268 kernel: xen: Mishandling of uninitialised FIFO-based event channel control blocks (xsa107)
CVE-2014-6268 kernel: xen: Mishandling of uninitialised FIFO-based event chan...
Status: CLOSED NOTABUG
Product: Security Response
Classification: Other
Component: vulnerability (Show other bugs)
unspecified
All Linux
medium Severity medium
: ---
: ---
Assigned To: Red Hat Product Security
impact=moderate,public=20140909,repor...
: Security
Depends On: 1140287
Blocks: 1140259
  Show dependency treegraph
 
Reported: 2014-09-10 11:50 EDT by Petr Matousek
Modified: 2015-02-16 10:43 EST (History)
18 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2014-09-10 11:53:23 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Petr Matousek 2014-09-10 11:50:53 EDT
When using the FIFO-based event channels, there are no checks for the
existence of a control block when binding an event or moving it to a
different VCPU. As a result, a buggy or malicious guest can crash the
host.

References:

http://xenbits.xen.org/xsa/advisory-107.html
http://www.openwall.com/lists/oss-security/2014/09/09/22

Acknowledgements:

Red Hat would like to thank the Xen for reporting this issue. Xen acknowledges
Vitaly Kuznetsov from Red Hat as the original reporter of this issue and David
Vrabel of Citrix as the one who diagnosed this issue as having security
repercussions.
Comment 3 Petr Matousek 2014-09-10 11:53:23 EDT
Statement:

Not vulnerable.

This issue did not affect the versions of the kernel-xen package as shipped with Red Hat Enterprise Linux 5.
Comment 4 Petr Matousek 2014-09-10 11:53:54 EDT
Created xen tracking bugs for this issue:

Affects: fedora-all [bug 1140287]

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