Multiple race conditions in the (1) virDomainBlockStats, (2) virDomainGetBlockInf, (3) qemuDomainBlockJobImpl, and (4) virDomainGetBlockIoTu
Multiple race conditions in the (1) virDomainBlockStats, (2) virDomainGetBlockInf, (3) qemuDomainBlockJobImpl, and (4) virDomainGetBlockIoTune functions in libvirt before 1.2.1 do not properly verify that the disk is attached, which allows remote read-only attackers to cause a denial of service (libvirtd crash) via the virDomainDetachDeviceFlags command.
- Published
- Jan 24, 2014
- Updated
- Jun 16, 2026
- EPSS
- 0.6% · 46th percentile
- CWE
- CWE-362
Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.
Report tools
Action score
27
Monitor
Low priority for now.
- CVSS
- 27 / 40 · 6.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.6%
Noroxi analysis
No Noroxi analysis for this record yet
We don't hand-write analysis for the hundreds of thousands of vulnerabilities in the database; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.
We use this product, ask for helpAffected systems
| Vendor | Product | CPE |
|---|---|---|
| redhat | libvirt | cpe:2.3:a:redhat:libvirt |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- redhat libvirtup to 1.2.0 inclusive
- redhat libvirt0.0.1
- redhat libvirt0.0.2
- redhat libvirt0.0.3
- redhat libvirt0.0.4
- redhat libvirt0.0.5
- redhat libvirt0.0.6
- redhat libvirt0.1.0
- redhat libvirt0.1.1
- redhat libvirt0.1.3
- redhat libvirt0.1.4
- redhat libvirt0.1.5
- redhat libvirt0.1.6
- redhat libvirt0.1.7
- redhat libvirt0.1.8
- redhat libvirt0.1.9
- redhat libvirt0.10.0
- redhat libvirt0.10.1
- redhat libvirt0.10.2
- redhat libvirt0.10.2.1
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | libvirt | before 1.2.1-1 | 1.2.1-1 |
| Debian:7 | libvirt | before 0.9.12.3-1 | 0.9.12.3-1 |
| Red Hat:enterprise_linux:6::client | libvirt | before 0:0.10.2-29.el6_5.3 | 0:0.10.2-29.el6_5.3 |
| Red Hat:enterprise_linux:6::client | libvirt-client | before 0:0.10.2-29.el6_5.3 | 0:0.10.2-29.el6_5.3 |
| Red Hat:enterprise_linux:6::client | libvirt-debuginfo | before 0:0.10.2-29.el6_5.3 | 0:0.10.2-29.el6_5.3 |
| Red Hat:enterprise_linux:6::client | libvirt-devel | before 0:0.10.2-29.el6_5.3 | 0:0.10.2-29.el6_5.3 |
| Red Hat:enterprise_linux:6::client | libvirt-lock-sanlock | before 0:0.10.2-29.el6_5.3 | 0:0.10.2-29.el6_5.3 |
| Red Hat:enterprise_linux:6::client | libvirt-python | before 0:0.10.2-29.el6_5.3 | 0:0.10.2-29.el6_5.3 |
Same product
redhat: all recordsOther highest-scoring records for the same primary product.
- CVE-2016-5008libvirt before 2.0.0 improperly disables password checking when the password on a VNC server is set to an empty string, which allows remote 40Plan
- CVE-2020-14339A flaw was found in libvirt, where it leaked a file descriptor for `/dev/mapper/control` into the QEMU process.35Monitor
- CVE-2019-10132A vulnerability was found in libvirt >= 4.1.0 in the virtlockd-admin.socket and virtlogd-admin.socket systemd units.35Monitor
- CVE-2013-4401The virConnectDomainXMLToNative API function in libvirt 1.1.0 through 1.1.3 checks for the connect:read permission instead of the connect:wr35Monitor
- CVE-2017-1000256libvirt version 2.3.0 and later is vulnerable to a bad default configuration of "verify-peer=no" passed to QEMU by libvirt resulting in a fa33Monitor
- CVE-2019-10168The virConnectBaselineHypervisorCPU() and virConnectCompareHypervisorCPU() libvirt APIs, 4.x.x before 4.10.1 and 5.x.x before 5.4.1, accept 31Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| debian:libvirt | 1.2.1-1 · Debian:12 | Package registry (OSV) |
| red hat:libvirt | 0:0.10.2-29.el6_5.3 · Red Hat:enterprise_linux:6::client | Package registry (OSV) |
| red hat:libvirt-client | 0:0.10.2-29.el6_5.3 · Red Hat:enterprise_linux:6::client | Package registry (OSV) |
| red hat:libvirt-debuginfo | 0:0.10.2-29.el6_5.3 · Red Hat:enterprise_linux:6::client | Package registry (OSV) |
| red hat:libvirt-devel | 0:0.10.2-29.el6_5.3 · Red Hat:enterprise_linux:6::client | Package registry (OSV) |
| red hat:libvirt-lock-sanlock | 0:0.10.2-29.el6_5.3 · Red Hat:enterprise_linux:6::client | Package registry (OSV) |
| red hat:libvirt-python | 0:0.10.2-29.el6_5.3 · Red Hat:enterprise_linux:6::client | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Special conditions such as timing or configuration are required.
If successful
- Confidentiality
- C · data can be read
- Integrity
- C · data or configuration can be modified
- Availability
- C · the service can be disrupted
- Attack complexity
- High
- Confidentiality impact
- C
- Integrity impact
- C
- Availability impact
- C
Weakness class (CWE)
CWE-362 · Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')CVSS vector
AV:A/AC:H/Au:N/C:C/I:C/A:C
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
- libvirt.org/news.html
- lists.opensuse.org/opensuse-updates/2014-02/msg00060.html
- lists.opensuse.org/opensuse-updates/2014-02/msg00062.html
- rhn.redhat.com/errata/RHSA-2014-0103.html
- secunia.com/advisories/56186
- secunia.com/advisories/56446
- secunia.com/advisories/60895
- security.gentoo.org/glsa/glsa-201412-04.xml
- www.debian.org/security/2014/dsa-2846
- www.ubuntu.com/usn/USN-2093-1
- bugzilla.redhat.com/show_bug.cgi?id=1043069
Vendor advisories and official records. Exploit/PoC links are deliberately left out.