vciy

CVE-2021-20196

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 NULL pointer dereference flaw was found in the floppy disk emulator of QEMU

CVE-2021-201964 of 4 sources documented this
21

rank 21 = 0 + 16 + 0 + 5 + 0

rank@v1 · backlog

Someone is already using it

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

EPSS 0.00479  ·  without this subject the record ranks 21

What it costs you if it fires

NVD CVSS base score, then the CNA's own

CVSS 6.5, from NVD  ·  without this subject the record ranks 5

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 21

How much of the world it touches

NVD CPE configurations

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

Someone else already set the date

CISA KEV remediation due date

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

Unaudited dollar value2 of 3 inputs carry a receipt
Exposure$14,600over the next 30 days, if this record is yours
Movementno material movementthe record holds only daily drift and scoring model releases
Basisassumeda published average, not your estate

$14,600 = $4.99M incident cost x 0.6121449559255632 exposure x 0.00479 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.00479EPSSNOT IN KEVas of 2026-09-20
Severity6.5 MEDIUMreceipt
Harmpartial impactreceipt
Exploitationnone in held sources
Defenseno fix version held
Movementfallenreceipt
PLATEAU10Minimal movement since 2021-05-27, 1894 days at 0.00, as of 2026-08-03. arc-rules@v1

Foresight · where to check next

No weakness class or product neighbourhood is held for this record, so this index cannot name anywhere to check next. That is an absence in the record, not a finding about the software.

Color is a claim, not decoration:the hostile worldthe defenseno signal

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 · low privileges required · no user interaction · low attack complexityreceipt
ImpactComplete availability loss, with impact beyond the vulnerable componentreceipt
Scored fromCVSS v3.1 · NVD's vectorreceipt
Weakness classCWE-476 NULL Pointer Dereferencereceipt
Published consequencesCWE-476: Availability: DoS: Crash, Exit, or Restart; Integrity, Confidentiality: Execute Unauthorized Code or Commands, Read Memory, Modify Memory[email protected]

CISA KEV & Federal Remediation Deadline from the record and CISA

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

Fixed inNo fix version in held sources, as the index stood on 3 Aug 2026.
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: Nothing observed in held sources.

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

Authority who says so

CVSS, NVD6.5 MEDIUMreceipt
Exploit probability0.00479 · top 60% of all CVEsreceipt
Blast breadth2 products across 2 vendorsderived
Assigned byredhatreceipt
Recorded changes24 · last 19 Sep 2026derived

Affected & Fixed Versions as published

Affected productqemureceipt
Published rangesqemu 5.2.0; debian linux 9.0; debian linux 10.0receipt

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 NULL pointer dereference flaw was found in the floppy disk emulator of QEMU. This issue occurs while processing read/write ioport commands if the selected floppy drive is not initialized with a block device. This flaw allows a privileged guest user to crash the QEMU process on the host, resulting in a denial of service. The highest threat from this vulnerability is to system availability. receipt

NVD's analysis a second authority

severity
6.5 CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:N/I:N/A:H
weakness
CWE-476
affected versions
qemu 5.2.0; debian linux 9.0; debian linux 10.0

check it yourself bugs.launchpad.net openwall.com security.netapp.com lists.debian.org lists.debian.org receipt

Movement the material steps

27 May 20210.00777
7 Mar 20235.6e-4 · scoring model v2023.03.01
17 Mar 20250.00034 · scoring model v2025.03.14
15 Jun 20260.00479 · scoring model v2026.06.15
3 Aug 20260.00479
Show all 24 observations
27 May 20210.00777
8 Jul 20210.01036
6 Jan 20220.04486
4 Feb 20220.01412
1 Apr 20220.0089
5 Apr 20220.0095
3 Feb 20230.01282
13 Feb 20230.0095
7 Mar 20235.6e-4
8 Mar 20230.00056
17 Mar 20250.00034
22 Mar 20250.00031
29 Mar 20250.00042
30 Mar 20250.00031
19 Oct 20250.00049
18 Nov 20250.00084
21 Nov 20250.00049
2 Dec 20250.00036
18 Feb 20260.00037
25 Feb 20260.00036
31 Mar 20260.00039
15 Jun 20260.00479
3 Jul 20260.00475
3 Aug 20260.00479

24 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.00479Published2021-05-26Index as of2026-08-03

The record had been public for 5 years, 2 months when this index was last written.

Published 2021-05-26 receipt · Index as of 2026-08-03 derived

Siblings and hubs

Records related to this one

Its defect family

qemu

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

Family membership: held values

Nothing we hold separates this record from the others in its defect family. 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-20196.

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.