CVE-2026-80817

UNRATEDCVSS · not yet scored

Also known asEUVD-2026-71252 (ENISA EUVD) · GHSA-wv8m-2pxf-rh83 (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:

iommu/iommufd: Fix NULL pointer deref in iommufd_ioas_change_process when racing with iopt_map_file_pages

iommufd_ioas_change_process() iterates every IOAS area while only holding every IOAS iova_rwsem, so it assumes every area has a non-NULL pages pointer. That assumption can be false when it runs concurrently with iopt_map_file_pages().

iopt_map_pages() executes in two phases. It first creates the area and inserts it into the interval tree under iova_rwsem, with area->pages still NULL. It then drops iova_rwsem and later fills area->pages under domains_rwsem. This leaves a window between area creation and area->pages fill where a concurrent iommufd_ioas_change_process() can observe the area and dereference a NULL area->pages pointer, leading to a NULL pointer dereference:

BUG: kernel NULL pointer dereference, address: 00000000000000c0 #PF: supervisor read access in kernel mode #PF: error_code(0x0000) - not-present page PGD 4b655067 P4D 4b655067 PUD 0 Oops: Oops: 0000 [#1] SMP NOPTI CPU: 0 UID: 0 PID: 11841 Comm: syz.1.628 Not tainted 7.1.0 #3 PREEMPT(full) Hardware name: QEMU Ubuntu 24.04 PC v2 (i440FX + PIIX, arch_caps fix, 1996), BIOS 1.16.3-debian-1.16.3-2 04/01/2014 RIP: 0010:iommufd_ioas_change_process+0x419/0xd50 drivers/iommu/iommufd/ioas.c:538 Code: 48 89 c3 48 85 c0 0f 84 cc 00 00 00 e8 10 f5 cb fd 48 8d 7b 68 e8 a7 b5 eb fd 48 8b 6b 68 48 8d bd c0 00 00 00 e8 17 b2 eb fd <8b> ad c0 00 00 00 bf 01 00 00 00 89 ee e8 85 ef cb fd 83 fd 01 74 RSP: 0018:ffffc90015c17d28 EFLAGS: 00010246 RAX: ffff8880186d5328 RBX: ffff88801d25e240 RCX: 0000000080000000 RDX: 00000000000002d7 RSI: ffffffff83ba9e10 RDI: 00000000000000c0 RBP: 0000000000000000 R08: ffffffff8e781eb8 R09: 0000000000000000 R10: 00000000000000c0 R11: ffffffff83ba9e29 R12: ffff88802e216008 R13: ffff88802e216000 R14: 0000000000000001 R15: 0000000000000000 FS: 00007f4aea3f66c0(0000) GS:ffff8880b1fa1000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00000000000000c0 CR3: 000000004b75c000 CR4: 0000000000350ef0 Call Trace: iommufd_fops_ioctl+0x287/0x400 drivers/iommu/iommufd/main.c:533 vfs_ioctl fs/ioctl.c:51 [inline] __do_sys_ioctl fs/ioctl.c:597 [inline] __se_sys_ioctl fs/ioctl.c:583 [inline] __x64_sys_ioctl+0x120/0x170 fs/ioctl.c:583 x64_sys_call+0x1092/0x1fb0 arch/x86/include/generated/asm/syscalls_64.h:17 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline] do_syscall_64+0x10a/0x680 arch/x86/entry/syscall_64.c:94 entry_SYSCALL_64_after_hwframe+0x77/0x7f RIP: 0033:0x7f4aec1a82bd Code: ff c3 66 2e 0f 1f 84 00 00 00 00 00 90 f3 0f 1e fa 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 b0 ff ff ff f7 d8 64 89 01 48 RSP: 002b:00007f4aea3f6018 EFLAGS: 00000246 ORIG_RAX: 0000000000000010 RAX: ffffffffffffffda RBX: 00007f4aec436090 RCX: 00007f4aec1a82bd RDX: 0000200000000180 RSI: 0000000000003b92 RDI: 0000000000000003 RBP: 00007f4aec250295 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000 R13: 00007f4aec436128 R14: 00007f4aec436090 R15: 00007ffd04ef23e0 Modules linked in: CR2: 00000000000000c0 ---[ end trace 0000000000000000 ]--- RIP: 0010:iommufd_ioas_change_process+0x419/0xd50 drivers/iommu/iommufd/ioas.c:538 Code: 48 89 c3 48 85 c0 0f 84 cc 00 00 00 e8 10 f5 cb fd 48 8d 7b 68 e8 a7 b5 eb fd 48 8b 6b 68 48 8d bd c0 00 00 00 e8 17 b2 eb fd <8b> ad c0 00 00 00 bf 01 00 00 00 89 ee e8 85 ef cb fd 83 fd 01 74 RSP: 0018:ffffc90015c17d28 EFLAGS: 00010246 RAX: ffff8880186d5328 RBX: ffff88801d25e240 RCX: 0000000080000000 RDX: 00000000000002d7 RSI: ffffffff83ba9e10 RDI: 00000000000000c0 RBP: 0000000000000000 R08: ffffffff8e781eb8 R09: 0000000000000000 R10: 00000000000000c0 R11: ffffffff83ba9e29 R12: ffff88802e216008 R13: ffff88802e216000 R14: 0000000000000001 R15: 0000000000000000 FS: 00007f4aea3f66c0(000 ---truncated---

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-80817(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 71 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:23 UTCEG score recompute
  12. 2026-10-19 09:23 UTCGHSA enrichmentGHSA-wv8m-2pxf-rh83
  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 44 more
  1. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  2. 2026-10-10 16:22 UTCGHSA enrichmentGHSA-wv8m-2pxf-rh83
  3. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  4. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  5. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  6. 2026-10-07 10:06 UTCGHSA enrichmentGHSA-wv8m-2pxf-rh83
  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 03:49 UTCGHSA enrichmentGHSA-wv8m-2pxf-rh83
  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-09-30 21:36 UTCEG score recompute
  15. 2026-09-30 21:36 UTCGHSA enrichmentGHSA-wv8m-2pxf-rh83
  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-27 15:21 UTCGHSA enrichmentGHSA-wv8m-2pxf-rh83
  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-24 14:04 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  23. 2026-09-24 08:51 UTCGHSA enrichmentGHSA-wv8m-2pxf-rh83
  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-21 21:09 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  27. 2026-09-21 02:37 UTCGHSA enrichmentGHSA-wv8m-2pxf-rh83
  28. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  29. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  30. 2026-09-17 20:23 UTCGHSA enrichmentGHSA-wv8m-2pxf-rh83
  31. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  32. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  33. 2026-09-15 03:12 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  34. 2026-09-14 11:06 UTCGHSA enrichmentGHSA-wv8m-2pxf-rh83
  35. 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  36. 2026-09-11 04:52 UTCGHSA enrichmentGHSA-wv8m-2pxf-rh83
  37. 2026-09-08 22:01 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  38. 2026-09-07 22:38 UTCEG score recompute
  39. 2026-09-07 22:38 UTCGHSA enrichmentGHSA-wv8m-2pxf-rh83
  40. 2026-09-06 13:48 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  41. 2026-09-05 15:31 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  42. 2026-09-04 16:22 UTCNVD update
  43. 2026-09-04 15:29 UTCEG score recompute
  44. 2026-09-04 15:29 UTCMITRE cvelistV5first tracked

Frequently asked(4)

What is CVE-2026-80817?
CVE-2026-80817 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: iommu/iommufd: Fix NULL pointer deref in iommufdioaschangeprocess when racing with ioptmapfilepages iommufdioaschange_process() iterates every IOAS area while only holding every IOAS iova_rwsem, so it assumes every area has a…
When was the CVE record for CVE-2026-80817 published?
The CVE record for CVE-2026-80817 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-80817 actively exploited?
CVE-2026-80817 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-80817?
A fix for CVE-2026-80817 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-80817 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-80817

Explore →

Is Your Infrastructure Affected by CVE-2026-80817?

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

Book a Demo →Browse All CVEs