RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 819636 - virsh heap corruption due to bad memmove
Summary: virsh heap corruption due to bad memmove
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: libvirt
Version: 6.3
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Eric Blake
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On: 638510
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-05-07 19:48 UTC by Eric Blake
Modified: 2012-06-20 06:58 UTC (History)
10 users (show)

Fixed In Version: libvirt-0.9.10-17.el6
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-06-20 06:58:12 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2012:0748 0 normal SHIPPED_LIVE Low: libvirt security, bug fix, and enhancement update 2012-06-19 19:31:38 UTC

Description Eric Blake 2012-05-07 19:48:05 UTC 
Description of problem:
Commit 35d52b56 (backported to 6.2 via bug 638510) had an off-by-three memmove, which can be used to cause a glibc abort.

Version-Release number of selected component (if applicable):
libvirt-0.9.10-16.el6

How reproducible:
100%

Steps to Reproduce:
1. $ valgrind virsh -c test:///default  snapshot-create-as test --print-xml --diskspec vda,file=a,,b
2.
3.
  
Actual results:
Note the 'invalid write of size 1' errors.
Running with MALLOC_PERTURB_ set to non-zero values can also be used to provoke heap corruption.


Expected results:
No invalid reads or writes.

Additional info:
Upstream patch:
https://www.redhat.com/archives/libvir-list/2012-May/msg00398.html
Comment 2 Eric Blake 2012-05-07 20:05:12 UTC 
In POST:
http://post-office.corp.redhat.com/archives/rhvirt-patches/2012-May/msg00156.html
Comment 4 Huang Wenlong 2012-05-09 08:32:28 UTC 
Verify this bug : 

libvirt-0.9.10-18.el6.x86_64

there is not  "invalid write of size 1" error

#valgrind virsh -c test:///default  snapshot-create-as test --print-xml --diskspec vda,file=a,,b

...
==29018== HEAP SUMMARY:
==29018==     in use at exit: 127,906 bytes in 1,362 blocks
==29018==   total heap usage: 6,496 allocs, 5,134 frees, 850,278 bytes allocated
==29018== 
==29018== LEAK SUMMARY:
==29018==    definitely lost: 0 bytes in 0 blocks
==29018==    indirectly lost: 0 bytes in 0 blocks
==29018==      possibly lost: 0 bytes in 0 blocks
==29018==    still reachable: 127,906 bytes in 1,362 blocks
==29018==         suppressed: 0 bytes in 0 blocks
==29018== Rerun with --leak-check=full to see details of leaked memory
==29018== 
==29018== For counts of detected and suppressed errors, rerun with: -v
==29018== Use --track-origins=yes to see where uninitialised values come from
==29018== ERROR SUMMARY: 45 errors from 10 contexts (suppressed: 8 from 6)
Comment 6 Min Zhan 2012-05-11 05:44:18 UTC 
Move it to VERIFIED per Comment 4.
Comment 8 errata-xmlrpc 2012-06-20 06:58:12 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHSA-2012-0748.html
Note You need to log in before you can comment on or make changes to this bug.