Race Condition Vulnerability in libvirt: Stack Use-After-Free Flaw

libvirt Updated 02 Oct 2025

Summary

08/05/2024
N/A
Yes i
Unrated
Not published

DEBIAN-CVE-2024-4418: A race condition leading to a stack use-after-free flaw was found in libvirt. Affects libvirt versions < 10.3.0-1. Fixed in 10.3.0-1. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

libvirt is an open-source API, daemon, and management tool for managing platform virtualization. It provides a consistent and stable interface for managing various virtualization technologies, including KVM, QEMU, and Xen. The package is widely used in cloud computing and virtualization environments. However, a recent vulnerability has been identified that could potentially allow unauthorized access to the virtproxyd daemon, compromising the security of systems using libvirt.

Vulnerability Detail

A race condition leading to a stack use-after-free flaw was discovered in libvirt. This issue arises from a faulty assumption in the virNetClientIOEventLoop() method, where a pointer to a stack-allocated virNetClientIOEventData structure is used in the virNetClientIOEventFD callback while the stack frame is concurrently being freed. This vulnerability allows a local, unprivileged user to access virtproxyd without authentication, potentially escaping their limited access rights. Remote users would still need to authenticate to access the service.

How To Fix

Minimum fixed version

10.3.0-1

This is the first release that contains the fix.

sudo apt-get install --only-upgrade libvirt

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Workaround

As a temporary workaround, consider restricting access to the virtproxyd daemon by implementing stricter access controls or disabling it until the package can be updated. This can be done by modifying the configuration files associated with libvirt to limit user permissions.

Conclusion

The identified race condition vulnerability in libvirt poses a significant risk by allowing unauthorized access to the virtproxyd daemon. It is crucial for users to update to the patched version 10.3.0-1 to secure their systems. Additionally, utilizing tools like Vulert can help monitor and manage vulnerabilities effectively.

See every vulnerability recorded for libvirt →

Share this vulnerability

FAQ

The vulnerability is a race condition that leads to a stack use-after-free flaw, potentially allowing unauthorized access to the virtproxyd daemon.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. Check your application against the vulnerability using the Vulert playground at Vulert Scanner.

If exploited, this vulnerability could allow local, unprivileged users to access sensitive services without authentication, leading to possible data breaches or unauthorized actions.

Yes, the vulnerability has been addressed in the libvirt package version 10.3.0-1. Updating to this version will fix the issue.

If an immediate update is not possible, implement stricter access controls on the virtproxyd daemon or disable it temporarily to mitigate risks.

Related vulnerabilities

Recent vulnerabilities recorded for libvirt.

How To Fix

Minimum fixed version

10.3.0-1

This is the first release that contains the fix.

sudo apt-get install --only-upgrade libvirt

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback