First published: Thu May 02 2024(Updated: )
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 | Affected Version | How to fix |
---|---|---|
libvirt |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
The severity of REDHAT-BUG-2278616 is considered high due to the potential for stack memory corruption.
To fix REDHAT-BUG-2278616, update to the latest version of libvirt where the vulnerability has been addressed.
REDHAT-BUG-2278616 affects systems running vulnerable versions of libvirt.
REDHAT-BUG-2278616 is caused by a race condition leading to a stack use-after-free bug in the libvirt library.
Currently, there is no official workaround for REDHAT-BUG-2278616 other than applying the recommended security updates.