CVE-2024-8235: Libvirt: crash of virtinterfaced via virconnectlistinterfaces()
A flaw was found in libvirt. A refactor of the code fetching the list of interfaces for multiple APIs introduced a corner case on platforms where allocating 0 bytes of memory results in a NULL pointer. This corner case would lead to a NULL-pointer dereference and subsequent crash of virtinterfaced. This issue could allow clients connecting to the read-only socket to crash the virtinterfaced daemon.
Other sources
A refactor of the code fetching the list of interfaces for multiple APIs introduced a corner case on platforms where allocating 0 bytes of memory results in a NULL pointer.
This corner case would lead to a NULL-pointer dereference and subsequent crash of virtinterfaced if virConnectListInterfaces() is called requesting 0 networks to be filled.
The bug was introduced in libvirt-10.4.0 and reproduces only on platforms where allocation of 0-length memory returns NULL instead of a valid pointer.
Upstream fix: https://gitlab.com/libvirt/libvirt/-/commit/8dfb12cb77996519901b8d52c754ab564ebd10e8
— Red Hat
Affected Software
Remediation
Event History
Frequently Asked Questions
What is the severity of CVE-2024-8235?
CVE-2024-8235 is classified with a medium severity due to the potential for causing a crash of the application.
How do I fix CVE-2024-8235?
To mitigate CVE-2024-8235, update libvirt to a version above 10.7.0, as this issue is fixed in later releases.
Which versions of libvirt are affected by CVE-2024-8235?
CVE-2024-8235 affects libvirt versions from 10.4.0 to 10.7.0.
On which platforms does CVE-2024-8235 occur?
CVE-2024-8235 occurs on platforms where allocating 0 bytes results in a NULL pointer.
What type of issue is CVE-2024-8235?
CVE-2024-8235 is a NULL-pointer dereference issue that can lead to application crashes.