CVE-2024-4418 | Libvirt: stack use-after-free in virnetclientioeventloop()

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.

Published: 2024-05-07 Last update: 2026-06-17 Assigner: [email protected] Source: [email protected]
NVD Status：Deferred，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2024-4418 is rated Low Risk (37.9/100): CVSS Medium severity, with low exploitation likelihood (EPSS 0.49%). Monitor for updates and reassess as exploit intelligence or EPSS changes.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2024-4418

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-06-15 0.63% 0.49% -0.14%
2 2026-05-27 0.54% 0.63% +0.09%
3 2025-11-21 — 0.54% —

Full EPSS history (17 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2024-4418

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
6.2 3.1 MEDIUM
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H Click to expand
Attack vector (AV:L)
They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 2.5 3.6 [email protected]

Weakness enumeration for CVE-2024-4418

OS Trackers for CVE-2024-4418

vendor priority summary link
debian unimportant CVE-2024-4418 unimportant priority: Debian including 1 source packages (libvirt), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 5. https://security-tracker.debian.org/tracker/CVE-2024-4418
redhat medium — https://access.redhat.com/security/cve/CVE-2024-4418
suse medium CVE-2024-4418 severity moderate: SUSE including 269 source package names (docker-28.3.2_ce-160000.3.1, docker-buildx-0.25.0-160000.3.1, …), 1128 product×package rows across 68 product lines (Container suse/manager/5.0/x86_64/server, Image SLE-Micro, … (68 product lines)): Known Not Affected 821, Fixed 307. https://www.suse.com/security/cve/CVE-2024-4418/
ubuntu medium CVE-2024-4418 medium priority: Ubuntu including 1 source packages (libvirt), 9 status rows across 9 suites (bionic, focal, jammy, mantic, noble, oracular, trusty, upstream, xenial): not-affected 6, released 2, needs-triage 1. https://ubuntu.com/security/CVE-2024-4418

Affected software / configurations for CVE-2024-4418

Vendor Product Version Raw CPE
No affected products in dataset.

References for CVE-2024-4418

cvelogic Threat Intelligence