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.
Credit: secalert@redhat.com secalert@redhat.com secalert@redhat.com
Affected Software | Affected Version | How to fix |
---|---|---|
debian/linux-2.6 | ||
All of | ||
Any of | ||
XenServer | <=3.3.2 | |
XenServer | =3.0.2 | |
XenServer | =3.0.3 | |
XenServer | =3.0.4 | |
XenServer | =3.1.3 | |
XenServer | =3.1.4 | |
XenServer | =3.2.0 | |
XenServer | =3.2.1 | |
XenServer | =3.2.2 | |
XenServer | =3.2.3 | |
XenServer | =3.3.0 | |
XenServer | =3.3.1 | |
Linux Kernel | =2.6.18 | |
XenServer | <=3.3.2 | |
XenServer | =3.0.2 | |
XenServer | =3.0.3 | |
XenServer | =3.0.4 | |
XenServer | =3.1.3 | |
XenServer | =3.1.4 | |
XenServer | =3.2.0 | |
XenServer | =3.2.1 | |
XenServer | =3.2.2 | |
XenServer | =3.2.3 | |
XenServer | =3.3.0 | |
XenServer | =3.3.1 | |
Linux Kernel | =2.6.18 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2010-4247 has been assessed with moderate severity due to its potential for excessive CPU consumption.
Fix CVE-2010-4247 by updating to the latest version of XenServer that includes the patch from changeset 391:77f831cbb91d.
CVE-2010-4247 affects XenServer versions up to 3.3.2, including specific versions 3.0.2 to 3.3.1.
CVE-2010-4247 is caused by the frontend passing a bad index of production request, resulting in an endless loop.
No, the vulnerability CVE-2010-4247 does not affect Linux kernel version 2.6.18.