Race Condition Affecting virt-devel:rhel/libvirt-daemon-driver-storage-disk package, versions <0:8.0.0-23.2.module+el8.10.0+21972+d7867348


Severity

Recommended
low

Based on Red Hat Enterprise Linux security rating.

Threat Intelligence

EPSS
0.05% (18th 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-RHEL8-VIRTDEVEL-7430649
  • published9 Jul 2024
  • disclosed2 May 2024

Introduced: 2 May 2024

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

How to fix?

Upgrade RHEL:8 virt-devel:rhel/libvirt-daemon-driver-storage-disk to version 0:8.0.0-23.2.module+el8.10.0+21972+d7867348 or higher.
This issue was patched in RHSA-2024:4351.

NVD Description

Note: Versions mentioned in the description apply only to the upstream virt-devel:rhel/libvirt-daemon-driver-storage-disk package and not the virt-devel:rhel/libvirt-daemon-driver-storage-disk package as distributed by RHEL. See How to fix? for RHEL:8 relevant fixed versions and status.

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.

CVSS Scores

version 3.1