REDHAT-BUG-980112: High severity libvirt libvirt vulnerability

Published Jul 1, 2013
·
Updated

Daniel P. Berrange reported:

"As non-root, simply run:

# virsh -c qemu:///system --readonly iface-list --inactive

The libvirtd daemon will crash with one of a number of different stack traces, for example:

Error in /home/berrange/src/virt/libvirt/daemon/.libs/lt-libvirtd': invalid fastbin entry (free): 0x00007f03fc02a1b0 ======= Backtrace: ========= /lib64/libc.so.6(+0x3cd5e7cef8)[0x7f0425cf7ef8] /home/berrange/src/virt/libvirt/src/.libs/libvirt.so.0(virFree+0x2e)[0x7f04293fd79e] /home/berrange/src/virt/libvirt/src/.libs/libvirt.so.0(virLogVMessage+0x37d)[0x7f042942384d] /home/berrange/src/virt/libvirt/src/.libs/libvirt.so.0(virLogMessage+0x97)[0x7f0429423b27] /home/berrange/src/virt/libvirt/src/.libs/libvirt.so.0(virObjectUnref+0x65)[0x7f04294324d5] /home/berrange/src/virt/libvirt/src/.libs/libvirt.so.0(virIdentitySetCurrent+0x35)[0x7f042941ae25] /home/berrange/src/virt/libvirt/src/.libs/libvirt.so.0(virNetServerProgramDispatch+0x392)[0x7f0429539be2] /home/berrange/src/virt/libvirt/src/.libs/libvirt.so.0(+0x195d68)[0x7f0429533d68] /home/berrange/src/virt/libvirt/src/.libs/libvirt.so.0(+0xa62e5)[0x7f04294442e5] /home/berrange/src/virt/libvirt/src/.libs/libvirt.so.0(+0xa594e)[0x7f042944394e] /lib64/libpthread.so.0(+0x3cd6207c53)[0x7f0426449c53] /lib64/libc.so.6(clone+0x6d)[0x7f0425d6fecd]

Looking at the code, we have a double-free of the 'struct netcfif' object when any of the filtering flags are set. Hence this only happens if you pass '--inactive' to virsh."

Upstream fix:

http://libvirt.org/git/?p=libvirt.git;a=commit;h=244e0b8cf15ca2ef48d82058e728656e6c4bad11

Acknowledgements:

This issue was discovered by Daniel P. Berrange of Red Hat.

Affected Software

1 affected component
libvirt libvirt

Event History

Jul 1, 2013
Data Sourced
via Red Hat·01:05 PM
DescriptionSeverityAffected Software
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of REDHAT-BUG-980112?

The severity of REDHAT-BUG-980112 is categorized as a critical issue due to a crash in the libvirtd daemon.

2

How do I fix REDHAT-BUG-980112?

To fix REDHAT-BUG-980112, update your libvirt installation to the latest version that addresses this bug.

3

What are the implications of REDHAT-BUG-980112 for users?

Users are at risk of disruption in virtualization management as the libvirtd daemon crashes when specific commands are executed.

4

Which versions of libvirt are affected by REDHAT-BUG-980112?

All versions of Red Hat libvirt before the patch addressing REDHAT-BUG-980112 are potentially affected.

5

Who reported REDHAT-BUG-980112?

REDHAT-BUG-980112 was reported by Daniel P. Berrange.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203