CVE-2026-80787

UNRATEDCVSS · not yet scored

Also known asEUVD-2026-71430 (ENISA EUVD) · GHSA-xprc-p39c-6w43 (GitHub Security Advisories)Source: ENISA EUVD

—
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • No CVSS published and no exploitation signals yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS v2: —Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

In the Linux kernel, the following vulnerability has been resolved:

nvmet: pci-epf: fix use-after-free in nvmet_pci_epf_exec_iod_work()

nvmet_pci_epf_exec_iod_work() submits an I/O command with req->execute() and then waits for the command to complete and transfers the data back to the host. This wait is not needed for commands that do not transfer data from the device to the host. To decide whether that wait is needed, it reads iod->data_len and iod->dma_dir after calling req->execute().

However, once req->execute() is called, the command may complete asynchronously on another CPU. For commands that do not require a device-to-host data transfer, nvmet_pci_epf_queue_response() calls nvmet_pci_epf_complete_iod() directly, which can free the iod before it reads iod->data_len and iod->dma_dir, resulting in the KFENCE use-after- free:

BUG: KFENCE: use-after-free read in nvmet_pci_epf_exec_iod_work+0x288/0x798 [nvmet_pci_epf]

Use-after-free read at 0x00000000fdfa6d03 (in kfence-#63): nvmet_pci_epf_exec_iod_work+0x288/0x798 [nvmet_pci_epf] process_one_work+0x15c/0x4f0 worker_thread+0x18c/0x30c kthread+0x130/0x140 ret_from_fork+0x10/0x20

kfence-#63: 0x00000000e3de0e71-0x00000000c938ad62, size=712, cache=kmalloc-1k

allocated by task 10 on cpu 0 at 73.995480s (0.005122s ago): mempool_kmalloc+0x1c/0x28 mempool_alloc_noprof+0x40/0x9c nvmet_pci_epf_poll_sqs_work+0xd4/0x344 [nvmet_pci_epf] process_one_work+0x15c/0x4f0 worker_thread+0x18c/0x30c kthread+0x130/0x140 ret_from_fork+0x10/0x20

freed by task 131 on cpu 3 at 73.995521s (0.008385s ago): mempool_kfree+0x10/0x20 mempool_free+0x44/0x64 nvmet_pci_epf_free_iod+0x88/0x98 [nvmet_pci_epf] nvmet_pci_epf_cq_work+0xfc/0x280 [nvmet_pci_epf] process_one_work+0x15c/0x4f0 worker_thread+0x18c/0x30c kthread+0x130/0x140 ret_from_fork+0x10/0x20

Fix this by referring to iod->data_len and iod->dma_dir before calling req->execute(). The remaining iod accesses such as iod->status are only reached on the device-to-host read path. In this case, nvmet_pci_epf_queue_response() signals iod->done instead of freeing the iod, so the iod stays valid.

CVSS v3
—
EchelonGraph score
Not yet assessedNo source has published severity data for this CVE yet — no CVSS score from NVD or a CNA, no GitHub advisory, and it is not in CISA KEV. This is not a rating of zero; we cannot assess it yet.
EG Score
—
EG Risk
—
EPSS PROB
0.2%
EPSS %ILE
10th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

EG Severity
Not assessed: no CVSS publishedA missing CVSS is not a severity of zero.
EG Likelihood
0.2% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-24). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
No SSVC decision: EchelonGraph has not assessed this CVECISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source: the BOD 26-04 block below.

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). Where an input reads “CISA's BOD 26-04 default”, no one has published it for this CVE, and CISA's implementation guidance says: “If “Automatable” and “Technical Impact” information items about a CVE ID are not available and the CVE ID is not in the KEV Catalog, CISA will treat its values as “no” and “total,” respectively, until CISA or a third party provides metadata about the CVE ID. CISA will always provide the Vulnrichment data for a CVE ID listed in the KEV Catalog.” Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

September 4, 2026

Last Modified

October 19, 2026

References (4)

Vendor Advisories for CVE-2026-80787(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(1 across 1 ecosystem)
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 7.1~rc7-1~exp1 (170 versions)
  • every version up to 7.1.12-1: fixed in 7.1.12-1
—

Data Freshness Timeline

(refreshed 8× in last 7d / 44× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 2 repeat rows among the latest 72 are merged into the row they repeat.

  1. 2026-10-26 16:32 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  2. 2026-10-25 16:34 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  3. 2026-10-25 13:59 UTCEG score recompute
  4. 2026-10-24 16:33 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  5. 2026-10-23 16:32 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  6. 2026-10-22 16:35 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  7. 2026-10-21 16:33 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  8. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  9. 2026-10-19 16:33 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  10. 2026-10-19 09:25 UTCNVD update
  11. 2026-10-19 09:25 UTCEG score recompute
  12. 2026-10-19 09:25 UTCGHSA enrichmentGHSA-xprc-p39c-6w43
  13. 2026-10-19 08:58 UTCMITRE cvelistV5
  14. 2026-10-18 16:33 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  15. 2026-10-18 03:09 UTCEG score recompute
  16. 2026-10-17 16:35 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  17. 2026-10-16 16:44 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  18. 2026-10-15 16:33 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  19. 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  20. 2026-10-13 16:35 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  21. 2026-10-12 16:35 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  22. 2026-10-12 14:57 UTCEG score recompute
  23. 2026-10-11 19:21 UTCEG score recompute
  24. 2026-10-11 16:37 UTCEG score recompute
  25. 2026-10-11 13:55 UTCEG score recompute
Show 45 more
  1. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  2. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  3. 2026-10-09 23:09 UTCGHSA enrichmentGHSA-xprc-p39c-6w43
  4. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  5. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  6. 2026-10-06 23:16 UTCGHSA enrichmentGHSA-xprc-p39c-6w43
  7. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  8. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  9. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  10. 2026-10-04 00:57 UTCGHSA enrichmentGHSA-xprc-p39c-6w43
  11. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  12. 2026-10-02 17:57 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  13. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  14. 2026-10-01 01:27 UTCEG score recompute
  15. 2026-10-01 01:27 UTCGHSA enrichmentGHSA-xprc-p39c-6w43
  16. 2026-09-30 15:04 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  17. 2026-09-28 13:52 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  18. 2026-09-28 03:07 UTCGHSA enrichmentGHSA-xprc-p39c-6w43
  19. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  20. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  21. 2026-09-26 00:28 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  22. 2026-09-25 04:47 UTCGHSA enrichmentGHSA-xprc-p39c-6w43
  23. 2026-09-24 14:04 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  24. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  25. 2026-09-22 16:01 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  26. 2026-09-22 06:28 UTCGHSA enrichmentGHSA-xprc-p39c-6w43
  27. 2026-09-21 21:09 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  28. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  29. 2026-09-19 08:07 UTCGHSA enrichmentGHSA-xprc-p39c-6w43
  30. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  31. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  32. 2026-09-16 09:48 UTCGHSA enrichmentGHSA-xprc-p39c-6w43
  33. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  34. 2026-09-15 03:12 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  35. 2026-09-13 11:28 UTCGHSA enrichmentGHSA-xprc-p39c-6w43
  36. 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  37. 2026-09-10 13:08 UTCGHSA enrichmentGHSA-xprc-p39c-6w43
  38. 2026-09-08 22:01 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  39. 2026-09-07 14:48 UTCEG score recompute
  40. 2026-09-07 14:48 UTCGHSA enrichmentGHSA-xprc-p39c-6w43
  41. 2026-09-06 13:48 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  42. 2026-09-05 15:31 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  43. 2026-09-04 16:22 UTCNVD update
  44. 2026-09-04 15:30 UTCEG score recompute
  45. 2026-09-04 15:29 UTCMITRE cvelistV5first tracked

Frequently asked(4)

What is CVE-2026-80787?
CVE-2026-80787 is a vulnerability whose severity is not yet rated; its CVE record was published on September 4, 2026. In the Linux kernel, the following vulnerability has been resolved: nvmet: pci-epf: fix use-after-free in nvmetpciepfexeciod_work() nvmetpciepfexeciod_work() submits an I/O command with req->execute() and then waits for the command to complete and transfers the data back to the host. This wait is…
When was the CVE record for CVE-2026-80787 published?
The CVE record for CVE-2026-80787 was published on September 4, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 19, 2026; the record at its source may have been updated since.
Is CVE-2026-80787 actively exploited?
CVE-2026-80787 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (10th percentile of EPSS-scored CVEs).
How do I remediate CVE-2026-80787?
A fix for CVE-2026-80787 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-80787 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-80787

Explore →

Is Your Infrastructure Affected by CVE-2026-80787?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs