CVE-2024-4418
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.
Scoring
- Severity
- MEDIUM
- CVSS base score
- 6.2
- CVSS vector
- CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
- EPSS probability
- 0.48%
- CWE
- CWE-562
- Published
- 2024-05-08
- Last modified
- 2026-03-13
Affected products
- Red Hat Red Hat Enterprise Linux 8
- Red Hat Red Hat Enterprise Linux 9
- Red Hat Red Hat Enterprise Linux 9.2 Extended Update Support
Weakness type
Related vulnerabilities
- CVE-2026-34553 — iccDEV: DoS in CIccCLUT::Iterate() & CIccMBB::Describe()
- CVE-2026-3591 — A stack use-after-return flaw in SIG(0) handling code may enable ACL bypass
- CVE-2024-33045 — Return of Stack Variable Address in Buses
- CVE-2022-41837 — An out-of-bounds write vulnerability exists in the OpenImageIO::add_exif_item_to_spec functionality...
- CVE-2021-21798 — An exploitable return of stack variable address vulnerability exists in the JavaScript...