REDHAT-BUG-2278616: Use After Free
A race condition leading to a stack use-after-free bug was found in libvirt. Due to a bad assumption in the virNetClientIOEventLoop() method, the data pointer to a stack-allocated virNetClientIOEventData structure ended up being used in virNetClientIOEventFD callback while the data pointer's stack frame was concurrently being "freed" when returning from virNetClientIOEventLoop().
Quoting libvirt maintainer Daniel P. Berrangé: The 'virtproxyd' daemon can be used to trigger requests which could potentially exercise the bug. If libvirt is configured with fine grained access control, this could in theory let a user escape their otherwise limited access. A local unprivileged user can access virtproxyd without authenticating. Remote users would need to authenticate before they could exercise it.
Affected Software
Event History
Frequently Asked Questions
What is the severity of REDHAT-BUG-2278616?
The severity of REDHAT-BUG-2278616 is considered high due to the potential for stack memory corruption.
How do I fix REDHAT-BUG-2278616?
To fix REDHAT-BUG-2278616, update to the latest version of libvirt where the vulnerability has been addressed.
What systems are impacted by REDHAT-BUG-2278616?
REDHAT-BUG-2278616 affects systems running vulnerable versions of libvirt.
What is the nature of the vulnerability in REDHAT-BUG-2278616?
REDHAT-BUG-2278616 is caused by a race condition leading to a stack use-after-free bug in the libvirt library.
Is there a workaround for REDHAT-BUG-2278616?
Currently, there is no official workaround for REDHAT-BUG-2278616 other than applying the recommended security updates.