Bug 656206 (CVE-2010-4247) - CVE-2010-4247 xen: request-processing loop is unbounded in blkback
Summary: CVE-2010-4247 xen: request-processing loop is unbounded in blkback
Alias: CVE-2010-4247
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
Depends On: 654546 656208
TreeView+ depends on / blocked
Reported: 2010-11-23 08:32 UTC by Eugene Teo (Security Response)
Modified: 2019-09-29 12:41 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2015-07-29 13:23:13 UTC

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2011:0004 0 normal SHIPPED_LIVE Important: kernel security, bug fix, and enhancement update 2011-01-04 16:52:05 UTC

Description Eugene Teo (Security Response) 2010-11-23 08:32:02 UTC
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@citrix.com>
date:        Fri Jan 18 16:52:25 2008 +0000
summary:     blkback: Request-processing loop is unbounded and hence requires a

changeset:   392:7070d34f251c
user:        Keir Fraser <keir.fraser@citrix.com>
date:        Mon Jan 21 11:43:31 2008 +0000
summary:     blkback/blktap: Check for kthread_should_stop() in inner loop,

Version-Release number of selected component (if applicable):

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.

Comment 4 errata-xmlrpc 2011-01-04 16:53:13 UTC
This issue has been addressed in following products:

  Red Hat Enterprise Linux 5

Via RHSA-2011:0004 https://rhn.redhat.com/errata/RHSA-2011-0004.html

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