Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 580426 - app-emulation/qemu: usb: Infinite loop vulnerability in usb_ehci using siTD process
Summary: app-emulation/qemu: usb: Infinite loop vulnerability in usb_ehci using siTD p...
Status: RESOLVED DUPLICATE of bug 568246
Alias: None
Product: Gentoo Security
Classification: Unclassified
Component: Vulnerabilities (show other bugs)
Hardware: All Linux
: Normal minor (vote)
Assignee: Gentoo Security
URL: https://lists.gnu.org/archive/html/qe...
Whiteboard: B3 [upstream]
Keywords:
Depends on:
Blocks:
 
Reported: 2016-04-18 13:28 UTC by Agostino Sarubbo
Modified: 2016-04-23 20:30 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Agostino Sarubbo gentoo-dev 2016-04-18 13:28:54 UTC
From ${URL} :

Qemu emulator built with the USB EHCI emulation support is vulnerable to an
infinite loop issue. It occurs during communication between host controller interface(EHCI) and a respective device driver. These two communicate via a split isochronous transfer descriptor list(siTD) and an infinite loop unfolds if there is a closed loop in this 
list.

A privileges used inside guest could use this flaw to consume excessive CPU cycles & resources on the host.

This issue is similar to CVE-2015-8558, but using siTD instead of iTD.

Upstream patch:
---------------
  -> https://lists.gnu.org/archive/html/qemu-devel/2016-04/msg02691.html

Reference:
----------
  -> http://www.openwall.com/lists/oss-security/2016/04/18/3


@maintainer(s): after the bump, in case we need to stabilize the package, please let us know if it is ready for the stabilization or not.
Comment 1 SpanKY gentoo-dev 2016-04-23 20:30:50 UTC
the referenced fix requires the fix for bug 568246 to be reverted.  since we didn't do that, the security issue isn't exposed.

they landed the change to fix behavior on FreeBSD, so i'll add what went into master (the revert+update).

*** This bug has been marked as a duplicate of bug 568246 ***