vciy

CVE-2015-6815

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.

The process_tx_desc function in hw/net/e1000.c in QEMU before 2.4.0.1 does not properly process transmit descriptor data when sending a network…

CVE-2015-68154 of 4 sources documented this
19

rank 19 = 0 + 9 + 0 + 10 + 0

rank@v1 · backlog

Someone is already using it

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

EPSS 0.00982  ·  without this subject the record ranks 19

What it costs you if it fires

NVD CVSS base score, then the CNA's own

CVSS 3.5, from NVD  ·  without this subject the record ranks 10

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 19

How much of the world it touches

NVD CPE configurations

20 products in the CPE ranges  ·  without this subject the record ranks 9

Someone else already set the date

CISA KEV remediation due date

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

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

$11,800 = $4.99M incident cost x 0.24048551839932833 exposure x 0.00982 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.00982EPSSNOT IN KEVas of 2026-09-20
Severity3.5 LOWreceipt
Harmpartial impactreceipt
Exploitationnone in held sources
Defenseunaffected versions publishedreceipt
Movementscoring model changedreceipt
PLATEAU10Minimal movement since 2022-02-04, 1592 days at 0.01, as of 2026-06-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 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.

Reachreachable from an adjacent network · low privileges required · no user interaction · low attack complexityreceipt
ImpactPartial 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.

First unaffected version, by branchqemu 2.4.0.1receipt
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, NVD3.5 LOWreceipt
Exploit probability0.00982 · top 39% of all CVEsreceipt
Blast breadth9 products across 5 vendorsderived
Assigned byredhatreceipt
Recorded changes15 · last 19 Sep 2026derived

Affected & Fixed Versions as published

Affected productQEMUreceipt
Published rangesqemu < 2.4.0.1; fedoraproject fedora 21; fedoraproject fedora 22; fedoraproject fedora 23receipt
Show all 20 published ranges
qemu < 2.4.0.1
fedoraproject fedora 21
fedoraproject fedora 22
fedoraproject fedora 23
novell suse linux enterprise software development kit 11.0
novell suse linux enterprise software development kit 12.0
novell suse linux enterprise debuginfo 11.0
novell suse linux enterprise desktop 11.0
novell suse linux enterprise desktop 12.0
novell suse linux enterprise server 11.0
novell suse linux enterprise server 12.0
canonical ubuntu linux 12.04
canonical ubuntu linux 14.04
canonical ubuntu linux 15.04
redhat openstack 5.0
redhat openstack 6.0
redhat openstack 7.0
redhat enterprise linux 5.0
redhat enterprise linux 6.0
redhat enterprise linux 7.0

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

The process_tx_desc function in hw/net/e1000.c in QEMU before 2.4.0.1 does not properly process transmit descriptor data when sending a network packet, which allows attackers to cause a denial of service (infinite loop and guest crash) via unspecified vectors. receipt

NVD's analysis a second authority

severity
3.5 CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L
weakness
CWE-835
affected versions
qemu < 2.4.0.1; fedoraproject fedora 21; fedoraproject fedora 22; and 17 more, listed in full below

check it yourself lists.opensuse.org lists.fedoraproject.org lists.fedoraproject.org lists.fedoraproject.org lists.opensuse.org lists.opensuse.org +7 morereceipt

Movement the material steps

4 Feb 20220.01547
7 Mar 20234.7e-4 · scoring model v2023.03.01
17 Mar 20250.02555 · scoring model v2025.03.14
15 Jun 20260.00982 · scoring model v2026.06.15
Show all 15 observations
4 Feb 20220.01547
7 Mar 20234.7e-4
8 Mar 20230.00047
24 Jan 20250.00065
17 Mar 20250.02555
19 Mar 20250.01897
29 Mar 20250.0519
30 Mar 20250.01897
1 Oct 20250.02246
27 Oct 20250.01897
28 Oct 20250.02246
27 Dec 20250.01897
28 Dec 20250.02246
19 Mar 20260.01574
15 Jun 20260.00982

15 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.00982Published2020-01-31Index as of2026-06-15

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

Published 2020-01-31 receipt · Index as of 2026-06-15 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-2015-6815.

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.