Libvirt: stack use-after-free in virnetclientioeventloop()
Summary
Libvirt: stack use-after-free in virnetclientioeventloop()
Original description
The description as published by the source.
A race condition leading to a stack use-after-free flaw 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 the virNetClientIOEventFD callback while the data pointer's stack frame was concurrently being "freed" when returning from virNetClientIOEventLoop(). The 'virtproxyd' daemon can be used to trigger requests. If libvirt is configured with fine-grained access control, this issue, in theory, allows a user to escape their otherwise limited access. This flaw allows a local, unprivileged user to access virtproxyd without authenticating. Remote users would need to authenticate before they could access it.
Fix status by distribution
Fixed packages published by each distribution for this CVE
- Debian DEBIAN-CVE-2024-4418 libvirt Fixed in: 10.3.0-1
References
- advisory access.redhat.com
- advisory access.redhat.com
- advisory access.redhat.com
- advisory access.redhat.com
- advisory github.com
- advisory nvd.nist.gov
- advisory security.netapp.com
- package gitlab.com
- report bugzilla.redhat.com
- web access.redhat.com
- web lists.fedoraproject.org
- web lists.fedoraproject.org