vciy

CVE-2021-3929

INDEX BUILT · 2026-09-20

No source can show you its own past. This one can.

Print this page to keep the view as it stands on this date. Everything hidden behind a disclosure opens, and every receipt prints with its value.

A DMA reentrancy issue was found in the NVM Express Controller (NVME) emulation in QEMU

CVE-2021-39294 of 4 sources documented this
41

rank 41 = 15 + 21 + 0 + 5 + 0

rank@v1 · scheduled

Someone is already using it

CISA KEV catalog · public proof-of-concept · FIRST EPSS

EPSS 0.00671  ·  without this subject the record ranks 26

What it costs you if it fires

NVD CVSS base score, then the CNA's own

CVSS 8.2, from NVD  ·  without this subject the record ranks 20

It is getting worse, not staying still

FIRST EPSS series, rescorings and bad loads removed

no persisting rise in 365 days  ·  without this subject the record ranks 41

How much of the world it touches

NVD CPE configurations

3 products in the CPE ranges  ·  without this subject the record ranks 36

Someone else already set the date

CISA KEV remediation due date

no CISA due date  ·  without this subject the record ranks 41

Unaudited dollar value2 of 3 inputs carry a receipt
Exposure$33,500over the next 30 days, if this record is yours
Movement-$640,000on 2025-03-30, the last material move, 1 year, 4 months before this reading
Basisassumeda published average, not your estate

$33,500 = $4.99M incident cost x 1 exposure x 0.00671 likelihood

udv@v1 · unaudited · wrong for you until you say what you run

$4.99M is the cost of a breach that happened, from IBM Cost of a Data Breach Report 2026, global average. It is not the value of any asset of yours. That average already covers breaches of every severity, so scaling it by exposure understates a partial-impact record. That is an assumption, not a measurement. Your own asset value goes in the decision record.

Hindsight · the state

0.00671EPSSNOT IN KEVas of 2026-09-20
Severity8.2 HIGHreceipt
Harmtotal lossreceipt
Exploitationpublic proof-of-conceptreceipt
Defenseunaffected versions publishedreceipt
Movementdoubled within 72hreceipt
PLATEAU10Minimal movement since 2025-03-30, 510 days at 0.01, as of 2026-08-22. arc-rules@v1

Foresight · where to check next

Microsoft WindowsLinux KernelPulse ConnectMicrosoft WindowsMicrosoft Windows3929

This record is one instance of CWE-416, use after free. The index holds 8701 prior instances of this class, 106 KEV-listed. The nearest of its KEV-listed records are drawn beside this. taxonomy@v1

Full pattern panel

Prior records in this weakness class. Each is its own record, dated and receipted.
Color is a claim, not decoration:the hostile worldthe defenseno signalspoke length is how much of the record matches, not how bad it is

Running QEMU? Check your version

A deterministic range check against the ranges this record publishes. It tells you where a version sits in the record, not whether your deployment is exploitable. No account needed.

Watch this record

Matches your own product list against every record this index holds, and tells you when one of them moves.

What counts as a move

Set up a watchlist (needs a Practitioner account)

Record your call

Keep your verdict, your reason and the evidence together. The record takes its date when you save it.

AcceptDeferPatch by…Not affectedMitigated

Choose your verdict, then sign in or use an email link. Your first 100 records are free. Evidence is frozen when the record is created.

Private to your organization unless you share it. Put the proof link in your ticket so a reviewer can inspect the basis for your call. See how decision records work.

Harm, if it fires from the vector and the weakness

Written for the ticket you're about to file.

Reachneeds local access · high privileges required · no user interaction · low attack complexityreceipt
ImpactComplete confidentiality, integrity and availability loss, with impact beyond the vulnerable componentreceipt
Scored fromCVSS v3.1 · NVD's vectorreceipt
Weakness classCWE-416 Use After Freereceipt
Published consequencesCWE-416: Integrity: Modify Memory; Availability: DoS: Crash, Exit, or Restart; Confidentiality: Read Memory; Integrity, Confidentiality, Availability: Execute Unauthorized Code or Commands[email protected]

CISA KEV & Federal Remediation Deadline from the record and CISA

The fix, and how long it's been waiting.

First unaffected version, by branchqemu 7.0.0receipt
Patch available sinceNo dated patch-availability record in held sources. The index holds reference URLs without dates and only the current revision of the CVE record, so the day a fix first existed cannot be derived. Only the versions it landed in.

Exploit Status & Known PoCs a ladder, not a score

Current rung: Proof-of-concept published · 1 public repository, 2022-05-13.

  • RUNG 1Nothing observed in held sources
  • RUNG 2Proof-of-concept published · 1 public repository2022-05-13receipt
  • RUNG 3Exploited in the wild · CISA KEV listed
  • RUNG 4Ransomware campaign use known

Authority who says so

CVSS, NVD8.2 HIGHreceipt
Exploit probability0.00671 · top 49% of all CVEsreceipt
Blast breadth2 products across 2 vendorsderived
Assigned byredhatreceipt
Recorded changes30 · last 19 Sep 2026derived

Affected & Fixed Versions as published

Affected productQEMUreceipt
Published rangesqemu < 7.0.0; fedoraproject fedora 35; fedoraproject fedora 36receipt

A rung lights from a row in the index, never from an assessment. "Held sources" is the true scope of the claim: this index reads the CVE record, NVD, CISA KEV, FIRST's EPSS and public proof-of-concept repositories, and it does not observe attacks.

Did this affect your environment?Answering needs an account.

What it is stated by the CNA

A DMA reentrancy issue was found in the NVM Express Controller (NVME) emulation in QEMU. This CVE is similar to CVE-2021-3750 and, just like it, when the reentrancy write triggers the reset function nvme_ctrl_reset(), data structs will be freed leading to a use-after-free issue. A malicious guest could use this flaw to crash the QEMU process on the host, resulting in a denial of service condition or, potentially, executing arbitrary code within the context of the QEMU process on the host. receipt

NVD's analysis a second authority

severity
8.2 CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H
weakness
CWE-416
affected versions
qemu < 7.0.0; fedoraproject fedora 35; fedoraproject fedora 36

check it yourself gitlab.com bugzilla.redhat.com access.redhat.com gitlab.com gitlab.com lists.fedoraproject.org receipt

Dated events

2025-03-17EPSS moved 0.00 to 0.102025-03-28EPSS moved 0.16 to 0.032025-03-30EPSS moved 0.16 to 0.03

Movement the material steps

26 Aug 20220.0095
7 Mar 20234.2e-4 · scoring model v2023.03.01
17 Mar 20250.10269 · crossed 0.10 · scoring model v2025.03.14
28 Mar 20250.02704 · crossed 0.10
29 Mar 20250.15529 · crossed 0.10
30 Mar 20250.02704 · crossed 0.10
15 Jun 20260.00643 · scoring model v2026.06.15
22 Aug 20260.00671

This score more than doubled inside 72 hours. Both observations are in the full history below.

Show all 27 observations
26 Aug 20220.0095
23 Sep 20220.01034
7 Mar 20234.2e-4
8 Mar 20230.00042
30 Nov 20230.00047
1 Apr 20240.00058
15 Apr 20240.00069
16 Nov 20240.00090
17 Mar 20250.10269
19 Mar 20250.15878
20 Mar 20250.10269
21 Mar 20250.10025
27 Mar 20250.15529
28 Mar 20250.02704
29 Mar 20250.15529
30 Mar 20250.02704
21 May 20250.0298
21 Jun 20250.03172
23 Jun 20250.04246
12 Sep 20250.0489
12 Oct 20250.04882
18 Nov 20250.02035
21 Nov 20250.04882
4 Jun 20260.04726
15 Jun 20260.00643
31 Jul 20260.00656
22 Aug 20260.00671

27 observations held. A highlighted step crossed a promotion threshold. A step marked with a scoring model moved because the instrument was replaced, not because the vulnerability changed. receipt

The full biography

EPSS 0.00671Public PoC2022-05-13Published2022-08-25Index as of2026-08-22

Exploit probability more than doubled between 2025-03-28 and 2025-03-29 (0.02704 → 0.15529) and the record had been public for 3 years, 11 months when this index was last written.

Public PoC 2022-05-13 receipt · Published 2022-08-25 receipt · Index as of 2026-08-22 derived

The pattern, elsewhere

This record is one instance of CWE-416, use after free. The index holds 8701 prior instances of this class, 106 KEV-listed. The nearest of its KEV-listed records are drawn beside this. [email protected]

CVE-2025-29824 · Microsoft Windows 10 Version 1507matches 6 of 9KEV listed · 2025receipt
CVE-2024-1086 · Linux Kernelmatches 6 of 9KEV listed · 2024receipt
CVE-2021-22893 · Pulse Connect Securematches 6 of 9KEV listed · 2021receipt
CVE-2021-40449 · Microsoft Windows 10 Version 1809matches 6 of 9KEV listed · 2021receipt
CVE-2025-21334 · Microsoft Windows 10 Version 21H2matches 6 of 9KEV listed · 2025receipt
CVE-2025-21335 · Microsoft Windows 10 Version 21H2matches 6 of 9KEV listed · 2025receipt

"Matches n of m" counts the attributes the two records can both be compared on: the CVSS metrics they share a version of, any weakness class beyond this one, and the vendor. fit-rules@v1

8701 records in this class held. The six above are drawn from the ones CISA has listed as exploited, ranked by how much of the record matches this one. That is why every one of them is KEV-listed: the pool is, so the colour on those spokes says nothing the pool has not already said.

No curated product neighbourhood is held for this product, so the records above are the nearest this index can name. The neighbourhood table covers a small set of products and is extended by hand.

Siblings and hubs

Records related to this one

Its defect family

qemu

Of the 7 records in this family that state one, this holds the highest EPSS percentile: 0.49604.

Grouped by shared product and weakness, not by shared vulnerability. Each record's own state is on its own page.

Family membership: held values

This record is one of a group, and the group's page describes all of them. This page is kept and dated, and the defect family's own page is the one we offer for indexing: the whole group.

Browse the index from here

These are index-wide views, not findings about CVE-2021-3929.

What usually comes next

Everything above needs no account. What is below is work: assembling it, scoping it to your estate, watching it, and handing it to someone else.

Everything on this page is free. Public data. Withholding it protects nothing.