Homepage

Return of Stack Variable Address The advisory has been revoked - it doesn't affect any version of package libvirt-daemon-driver-storage  (opens in a new tab)

Threat Intelligence

EPSS
0.49% (40th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-RHEL9-LIBVIRTDAEMONDRIVERSTORAGE-11475339
  • published5 Aug 2025
  • disclosed2 May 2024
Report a new vulnerability Found a mistake?

Introduced: 2 May 2024

CVE-2024-4418  (opens in a new tab)
CWE-562  (opens in a new tab)

Amendment

The Red Hat security team deemed this advisory irrelevant for RHEL:9.

NVD Description

Note: Versions mentioned in the description apply only to the upstream libvirt-daemon-driver-storage package and not the libvirt-daemon-driver-storage package as distributed by RHEL.

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.