CVE-2024-4418
Description
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.
How to fix
- libvirt10.4.0 or later
Affected products
| Product | Affected versions | Fixed in |
|---|---|---|
| libvirt | v < 10.4.0 | 10.4.0 |
| enterprise_linux 8 | No range specified | — |
| enterprise_linux 9 | No range specified | — |
| rhel_eus 9.2 | No range specified | — |
| advanced_virtualization 8 | No range specified | — |
Check your version
Choose the product and enter the version you run to see whether it falls in the affected range.
Attack Surface Management
See the assets tied to your domains, the technologies they run and known vulnerabilities in one list.