This is an automatically created tracking bug! It was created to ensure
that one or more security vulnerabilities are fixed in affected Fedora
For comments that are specific to the vulnerability please use bugs filed
against "Security Response" product referenced in the "Blocks" field.
For more information see:
When creating a Bodhi update request, please include the bug IDs of the
respective parent bugs filed against the "Security Response" product.
Please mention CVE ids in the RPM changelog when available.
Bodhi update submission link:
Please note: this issue affects multiple supported versions of Fedora.
Only one tracking bug has been filed; please only close it when all
affected versions are fixed.
[bug automatically created by: add-tracking-bugs]
Fixed by this upstream patch:
Author: Eric Blake <firstname.lastname@example.org>
Date: Fri Jun 24 12:16:05 2011 -0600
remote: protect against integer overflow
Integer overflow and remote code are never a nice mix.
This has existed since commit 56cd414.
* src/libvirt.c (virDomainGetVcpus): Reject overflow up front.
* src/remote/remote_driver.c (remoteDomainGetVcpus): Avoid overflow
on sending rpc.
* daemon/remote.c (remoteDispatchDomainGetVcpus): Avoid overflow on
F14 and F15 can instead use this backport, to avoid having to update gnulib:
Rawhide will pick up the fix by rebasing to 0.9.3.
libvirt-0.8.8-7.fc15 has been submitted as an update for Fedora 15.
libvirt-0.8.3-10.fc14 has been submitted as an update for Fedora 14.
* should fix your issue,
* was pushed to the Fedora 15 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing libvirt-0.8.8-7.fc15'
as soon as you are able to.
Please go to the following url:
then log in and leave karma (feedback).
libvirt-0.8.8-7.fc15 has been pushed to the Fedora 15 stable repository. If problems still persist, please make note of it in this bug report.
libvirt-0.8.3-10.fc14 has been pushed to the Fedora 14 stable repository. If problems still persist, please make note of it in this bug report.