vciy

CVE-2021-28698

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.

long running loops in grant table handling In order to properly monitor resource use, Xen maintains information on the grant mappings a domain may…

CVE-2021-286984 of 4 sources documented this
20

rank 20 = 0 + 14 + 0 + 6 + 0

rank@v1 · backlog

Someone is already using it

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

EPSS 0.00351  ·  without this subject the record ranks 20

What it costs you if it fires

NVD CVSS base score, then the CNA's own

CVSS 5.5, from NVD  ·  without this subject the record ranks 6

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 20

How much of the world it touches

NVD CPE configurations

5 products in the CPE ranges  ·  without this subject the record ranks 14

Someone else already set the date

CISA KEV remediation due date

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

Unaudited dollar value2 of 3 inputs carry a receipt
Exposure$10,700over 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

$10,700 = $4.99M incident cost x 0.6121449559255632 exposure x 0.00351 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.00351EPSSNOT IN KEVas of 2026-09-20
Severity5.5 MEDIUMreceipt
Harmpartial impactreceipt
Exploitationnone in held sources
Defensefix version namedreceipt
Movementdoubled within 72hreceipt
PLATEAU10Minimal movement since 2021-08-28, 1782 days at 0.00, as of 2026-07-15. 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 xen? 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 lossreceipt
Scored fromCVSS v3.1 · NVD's vectorreceipt
Weakness classCWE-835 Loop with Unreachable Exit Condition ('Infinite Loop')receipt
Published consequencesCWE-835: Availability: DoS: Resource Consumption (CPU), DoS: Resource Consumption (Memory), DoS: Amplification[email protected]

CISA KEV & Federal Remediation Deadline from the record and CISA

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

Fixed in4.12receipt
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, NVD5.5 MEDIUMreceipt
Exploit probability0.00351 · top 71% of all CVEsreceipt
Blast breadth3 products across 3 vendorsderived
Assigned byXENreceipt
Recorded changes21 · last 19 Sep 2026derived

Affected & Fixed Versions as published

Affected productxenreceipt
Published rangesxen >= 3.2.0; fedoraproject fedora 33; fedoraproject fedora 34; fedoraproject fedora 35receipt
Show all 5 published ranges
xen >= 3.2.0
fedoraproject fedora 33
fedoraproject fedora 34
fedoraproject fedora 35
debian linux 11.0
Fixed in4.12receipt

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

long running loops in grant table handling In order to properly monitor resource use, Xen maintains information on the grant mappings a domain may create to map grants offered by other domains. In the process of carrying out certain actions, Xen would iterate over all such entries, including ones which aren't in use anymore and some which may have been created but never used. If the number of entries for a given domain is large enough, this iterating of the entire table may tie up a CPU for too long, starving other domains or causing issues in the hypervisor itself. Note that a domain may map its own grants, i.e. there is no need for multiple domains to be involved here. receipt

Read the rest of the CNA's description

A pair of "cooperating" guests may, however, cause the effects to be more severe.

NVD's analysis a second authority

severity
5.5 CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
weakness
CWE-835
affected versions
xen >= 3.2.0; fedoraproject fedora 33; fedoraproject fedora 34; and 2 more, listed in full below

check it yourself xenbits.xenproject.org openwall.com lists.fedoraproject.org lists.fedoraproject.org debian.org lists.fedoraproject.org +1 morereceipt

Movement the material steps

28 Aug 20210.00416
7 Mar 20234.5e-4 · scoring model v2023.03.01
17 Mar 20250.00042 · scoring model v2025.03.14
15 Jun 20260.00337 · scoring model v2026.06.15
15 Jul 20260.00351

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

Show all 21 observations
28 Aug 20210.00416
1 Sep 20210.00624
2 Sep 20210.02742
6 Sep 20210.04504
22 Sep 20210.05363
25 Sep 20210.06208
10 Oct 20210.01454
6 Jan 20220.06208
4 Feb 20220.02008
1 Apr 20220.01034
7 Mar 20234.5e-4
8 Mar 20230.00045
17 Mar 20250.00042
19 Mar 20250.00041
29 Mar 20250.00088
30 Mar 20250.00041
15 Aug 20250.00076
16 Aug 20250.00056
15 Jun 20260.00337
20 Jun 20260.00348
15 Jul 20260.00351

21 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.00351Published2021-08-27Index as of2026-07-15

Exploit probability more than doubled between 2021-09-01 and 2021-09-02 (0.00624 → 0.02742) and the record had been public for 4 years, 10 months when this index was last written.

Published 2021-08-27 receipt · Index as of 2026-07-15 derived

Siblings and hubs

Records related to this one

Browse the index from here

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

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.