REDHAT-BUG-656206
First published: Tue Nov 23 2010(Updated: )
If the frontend pass a bad index of production request, the backend will enter an endless loop and then cause a excessive CPU consumption. This issue has been fixed in upstream by: changeset: 391:77f831cbb91d user: Keir Fraser <keir.fraser> date: Fri Jan 18 16:52:25 2008 +0000 summary: blkback: Request-processing loop is unbounded and hence requires a <a href="http://xenbits.xensource.com/linux-2.6.18-xen.hg?rev/77f831cbb91d">http://xenbits.xensource.com/linux-2.6.18-xen.hg?rev/77f831cbb91d</a> changeset: 392:7070d34f251c user: Keir Fraser <keir.fraser> date: Mon Jan 21 11:43:31 2008 +0000 summary: blkback/blktap: Check for kthread_should_stop() in inner loop, <a href="http://xenbits.xensource.com/linux-2.6.18-xen.hg?rev/7070d34f251c">http://xenbits.xensource.com/linux-2.6.18-xen.hg?rev/7070d34f251c</a> Version-Release number of selected component (if applicable): 2.6.18-194.el5xen How reproducible: Steps to Reproduce: 1. build a guest kernel with the patch attached. 2. run domU with the patched kernel Actual results: Dom0 got hung. Expected results: Dom0 shouldn't be impacted by a bad guest.
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Xen Hypervisor |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the severity of REDHAT-BUG-656206?
The severity of REDHAT-BUG-656206 is high due to excessive CPU consumption caused by an endless loop.
How do I fix REDHAT-BUG-656206?
To fix REDHAT-BUG-656206, ensure you update to the patched version of the Xen Hypervisor that includes the fix implemented by the upstream changeset.
What platforms are affected by REDHAT-BUG-656206?
REDHAT-BUG-656206 affects the Xen Hypervisor running on Red Hat systems.
What is the cause of the issue in REDHAT-BUG-656206?
The issue in REDHAT-BUG-656206 occurs when the frontend passes a bad index in a production request, leading to an endless loop.
Who is responsible for the fix for REDHAT-BUG-656206?
The fix for REDHAT-BUG-656206 was developed by Keir Fraser as part of the upstream changeset.
- agent/references
- agent/type
- agent/first-publish-date
- agent/last-modified-date
- collector/redhat-bugzilla
- source/Red Hat
- alias/CVE-2010-4247
- agent/source
- agent/severity
- agent/description
- agent/event
- agent/softwarecombine
- agent/tags
- agent/guess-ai
- agent/software-canonical-lookup
- agent/software-canonical-lookup-request
- vendor/xen
- canonical/xen hypervisor