Security Resilience

CVE-2023-3301

Race Condition in Qemu ≤ 8.0.3

Published
13 September 2023
Modified
21 November 2024
Patch / advisory
CVSS Score v3.1 5.6
Click a component to see what it means
Raw vectorCVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:C/C:N/I:N/A:H
EPSS Score 0.0026 18th percentile
Risk Priority 40 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). EPSS, Forum of Incident Response and Security Teams (FIRST), epss.first.org. Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2023-3301 is a medium-severity Reachable Assertion (CWE-617) vulnerability in Qemu. Its CVSS base score is 5.6 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Endpoint Denial of Service (T1499); ranked at the 18th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

A flaw was found in QEMU. The async nature of hot-unplug enables a race scenario where the net device backend is cleared before the virtio-net pci frontend has been unplugged. A malicious guest could use this time window to trigger…

more

an assertion and cause a denial of service.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

MITRE ATT&CK v20.0

T1499 Endpoint Denial of Service Impact
Adversaries may perform Endpoint Denial of Service (DoS) attacks to degrade or block the availability of services to users.
T1499.004 Application or System Exploitation Impact
Adversaries may exploit software vulnerabilities that can cause an application or system to crash and deny availability to users.
T1687 Exploitation for Defense Impairment Defense Impairment
Adversaries may exploit vulnerabilities in security software, infrastructure, or defensive components to degrade, disable, or otherwise continue to impair their ability to prevent, detect, or respond to malicious activity.
T1685 Disable or Modify Tools Defense Impairment
Adversaries may disable, degrade, or tamper with security tools or applications (e.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2024-3567Same product: Qemu Qemu
CVE-2024-8354Same product: Qemu Qemu
CVE-2023-6683Same product: Qemu Qemu
CVE-2023-2680Same product: Qemu Qemu
CVE-2023-3019Same product: Qemu Qemu
CVE-2024-6505Same product: Qemu Qemu
CVE-2023-5088Same product: Qemu Qemu
CVE-2023-5871Shared CWE-617
CVE-2023-3255Same product: Qemu Qemu
CVE-2023-38470Shared CWE-617

Affected Assets

qemu
qemu
≤ 8.0.3
redhat
enterprise linux
8.0, 9.0

Mitigating Controls

Likely Mitigating Controls

Our mappings. Per-CVE control mapping for this CVE has not run yet; the list below is derived from the weakness types (CWEs) cited in the NVD entry.

addresses: CWE-362

Accurate timestamps from internal clocks enable detection of race conditions by providing reliable event ordering in audit logs.

addresses: CWE-362

Coordination of concurrent security activities reduces the probability that shared resources will be accessed simultaneously without proper synchronization.

Mitigating Controls (NIST CSF 2.0)

Our mappings, derived directly from the weakness types (CWEs) cited in the NVD entry via our CWE→CSF cross-walk — links open the control.

PR.PS-06 mostly match
blocks

Secure SDLC practices directly prevent unsafe assertions from being coded in reachable paths.

DE.CM-09 partial match
blocks

Runtime monitoring of software can detect assertion-triggered crashes as adverse events.

ID.RA-01 partial match
blocks

Vulnerability identification processes can discover and record reachable-assertion flaws before deployment.

Mitigating Controls (ISO/IEC 27001:2022 Annex A)

Our mappings, derived directly from the weakness types (CWEs) cited in the NVD entry via our CWE→ISO cross-walk — links open the control.

finds

Security testing in development can detect reachable assertions before release, reducing the likelihood of exploitation.

finds

A.5.26 item (j) explicitly mandates identifying vulnerabilities and weaknesses that caused or contributed to an incident, so post-incident analysis can locate the specific reachable assertion in code after a triggered DoS — but this is a reactive path that only finds instances which have already been triggered, reported, and investigated to the code level, leaving the bulk of latent CWE-617 instances (never triggered, or triggered without deep root-cause analysis) undiscovered.

prevents

Training developers about secure coding practices (including not using assert() for input validation in production) reduces some instances of reachable assertions, but the practice is fallible and the specific implementation detail requires targeted knowledge that general awareness only partially delivers.

prevents

Secure coding standards explicitly ban the use of assert() or equivalent statements that can be triggered by external input.

finds

A.8.8's reach is DISCLOSURE — it sees only vendor-published flaws, and the disclosed share of any weakness class is a minority, capping `finds` at `partial`. CWE-617 does surface as CVEs (multiple observed examples), so the disclosed portion is findable, but the bulk of latent reachable assertions in deployed code never carries a vendor advisory.

Hardening callouts derived

DISA STIG baselines are authored against specific weaknesses. Where this CVE cites a broad weakness class, the mapping is not asserted at that abstraction (owner ruling, 2026-09-25: grade only at Base and below), so no rule is shown here rather than a rule shown against the wrong grain.

  • No fine-grained STIG row for CWE-362, a class-level weakness, and none of its children carries one either.

References