CVE-2026-98216

HIGHPre-NVD 7.17.1
EchelonGraph scoreHIGH confidence

“—” beside the score: it is equal to the CVSS score beside it.

Score 7.1 from GitHub Security Advisory (severity: HIGH) published 2026-10-06. A secondary CVSS source baseline 7.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Trending — 4 sources updated this week
7.1EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.1%CVSS: 7.1Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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

IB/hfi1: Fix the PIO_CRED credit-return mmap

hfi1_file_mmap()'s PIO_CRED case must hand user space the single credit-return page that holds this context's entry. That page is the second or third page of the per-node credit-return allocation once the hardware send context index reaches 64 or 128, so the failure below is intermittent: when the entry lands on the first page the offset is zero and everything works.

Two things are wrong.

First, cr_page_offset is a byte offset but .va is a struct credit_return *, so adding it is pointer arithmetic and scales the offset by sizeof(struct credit_return) == 64. memvirt then lands 256 KiB or 512 KiB past a 10240-byte allocation. With an IOMMU translating, that address is inside the vmalloc range but in no vm_area, so dma_mmap_coherent() -> iommu_dma_mmap() finds no pages, vmalloc_to_pfn() returns page_to_pfn(NULL), and remap_pfn_range() installs a frame above MAXPHYADDR. The first user read then takes:

psm2_ep_open_pr: Corrupted page table at address 7a14d007e000 PGD 800000013886a067 P4D 800000013886a067 PUD 13886b067 PMD 13886c067 PTE 800049168e911235 Oops: Bad pagetable: 000d [#1] SMP PTI

Second, and still wrong once the arithmetic is corrected, dma_mmap_coherent() describes a whole coherent buffer and selects the page within it with vma->vm_pgoff. Offsetting cpu_addr has no effect: for a vmap'd allocation iommu_dma_mmap() uses cpu_addr only to locate the vm_area and then maps pages[vm_pgoff], which hfi1_file_mmap() has just set to 0. User space therefore always receives the first credit-return page, every credit read is for the wrong context, and send PIO stalls forever.

Use the DMA API as intended: pass the base of the allocation with its full length and select the page with vm_pgoff. A separate length is needed because memlen must keep describing the VMA for the existing size check. The dma-direct path stays correct as well, since dma_direct_mmap() adds the same vm_pgoff to the base pfn.

Tested on a Dell T7610 (Xeon E5-2650 v2, Intel IOMMU in DMA-FQ mode) against a Threadripper PRO 3995WX peer, both Omni-Path 100. Before this change psm2_ep_open() Oopses the kernel; with only the arithmetic corrected psm2_ep_open() succeeds but any transfer that uses send PIO hangs, PSM2_SDMA=2 (send PIO disabled) completing normally while PSM2_SDMA=0 (send PIO only) hangs every time. With this change send PIO, send DMA and the default mixed mode all work.

CVSS v3
7.1
EG Score
7.1HIGHhigh confidence
EG Risk
32
EG Risk 32/100

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed (value × EchelonGraph’s weight)
Severity71% × 45%
The EG Score, 7.1 of 10.
Exploitation0.1% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's BOD 26-04 default: no one has published Automatable for this CVE, and CISA treats it as “no” for a CVE not in KEV.
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from Vulnrichment. EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.1%
EPSS %ILE
2nd
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from Vulnrichment. EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

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

October 6, 2026

Last Modified

October 7, 2026

Advisory Details (5)

Auto-updated Oct 7, 2026
Patch available.
Web page

IB/hfi1: Fix the PIO_CRED credit-return mmap - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/62f0f34fbd2b2d5653d33d3b9d42fdcabb1c0101
Web page

IB/hfi1: Fix the PIO_CRED credit-return mmap - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/bafeac9ce5d1ce5256bcf7e5702e831e9aaf419b
Web page

IB/hfi1: Fix the PIO_CRED credit-return mmap - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/180752deb7270ad37394ab6ef7cf4978fad040b3
Web page

IB/hfi1: Fix the PIO_CRED credit-return mmap - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/dcebe0b0bb080a25fe08011fd6b6e741f7912f01
Web page

IB/hfi1: Fix the PIO_CRED credit-return mmap - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/535530bb2ea5254e1e9f55280143d262dd065204

Vendor Advisories for CVE-2026-98216(2)

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

Affected Packages

(2 across 2 ecosystems)
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 7.2~rc7-1~exp1 (183 versions)
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 7.2~rc7-1~exp1 (181 versions)
  • every version up to 7.2.8-1: fixed in 7.2.8-1
—

Data Freshness Timeline

(refreshed 39× in last 7d / 50× 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.

  1. 2026-10-13 16:35 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  2. 2026-10-13 03:58 UTCEG score recompute
  3. 2026-10-13 03:58 UTCVendor advisory
  4. 2026-10-13 03:58 UTCGHSA enrichmentGHSA-2p8w-fgw9-p46c · GitHub severity HIGH · GitHub CVSS 7.1
  5. 2026-10-12 16:35 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  6. 2026-10-12 14:38 UTCEG score recompute
  7. 2026-10-11 22:10 UTCVendor advisory
  8. 2026-10-11 22:09 UTCGHSA enrichmentGHSA-2p8w-fgw9-p46c · GitHub severity HIGH · GitHub CVSS 7.1
  9. 2026-10-11 19:10 UTCEG score recompute
  10. 2026-10-11 16:25 UTCEG score recompute
  11. 2026-10-11 13:50 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  12. 2026-10-11 13:37 UTCEG score recompute
  13. 2026-10-11 11:08 UTCVendor advisory
  14. 2026-10-11 11:08 UTCGHSA enrichmentGHSA-2p8w-fgw9-p46c · GitHub severity HIGH · GitHub CVSS 7.1
  15. 2026-10-11 00:08 UTCEG score recompute
  16. 2026-10-11 00:08 UTCVendor advisory
  17. 2026-10-11 00:08 UTCGHSA enrichmentGHSA-2p8w-fgw9-p46c · GitHub severity HIGH · GitHub CVSS 7.1
  18. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  19. 2026-10-10 13:06 UTCVendor advisory
  20. 2026-10-10 13:06 UTCGHSA enrichmentGHSA-2p8w-fgw9-p46c · GitHub severity HIGH · GitHub CVSS 7.1
  21. 2026-10-10 02:06 UTCEG score recompute
  22. 2026-10-10 02:06 UTCVendor advisory
  23. 2026-10-10 02:06 UTCGHSA enrichmentGHSA-2p8w-fgw9-p46c · GitHub severity HIGH · GitHub CVSS 7.1
  24. 2026-10-09 20:08 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  25. 2026-10-09 15:04 UTCVendor advisory
Show 25 more
  1. 2026-10-09 15:04 UTCGHSA enrichmentGHSA-2p8w-fgw9-p46c · GitHub severity HIGH · GitHub CVSS 7.1
  2. 2026-10-09 03:44 UTCEG score recompute
  3. 2026-10-09 03:44 UTCVendor advisory
  4. 2026-10-09 03:44 UTCGHSA enrichmentGHSA-2p8w-fgw9-p46c · GitHub severity HIGH · GitHub CVSS 7.1
  5. 2026-10-08 17:14 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  6. 2026-10-08 16:45 UTCVendor advisory
  7. 2026-10-08 16:45 UTCGHSA enrichmentGHSA-2p8w-fgw9-p46c · GitHub severity HIGH · GitHub CVSS 7.1
  8. 2026-10-08 05:29 UTCEG score recompute
  9. 2026-10-08 05:29 UTCVendor advisory
  10. 2026-10-08 05:29 UTCGHSA enrichmentGHSA-2p8w-fgw9-p46c · GitHub severity HIGH · GitHub CVSS 7.1
  11. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  12. 2026-10-07 18:29 UTCEG score recompute
  13. 2026-10-07 18:29 UTCVendor advisory
  14. 2026-10-07 18:29 UTCGHSA enrichmentGHSA-2p8w-fgw9-p46c · GitHub severity HIGH · GitHub CVSS 7.1
  15. 2026-10-07 07:29 UTCEG score recompute
  16. 2026-10-07 07:29 UTCVendor advisory
  17. 2026-10-07 07:29 UTCGHSA enrichmentGHSA-2p8w-fgw9-p46c
  18. 2026-10-07 06:58 UTCEG score recomputeFirst assessed: 7.1 HIGH
  19. 2026-10-07 06:58 UTCGHSA enrichmentGHSA-2p8w-fgw9-p46c
  20. 2026-10-07 06:56 UTCMITRE cvelistV5CVSS v3 → 7.1 · severity → HIGH
  21. 2026-10-06 15:19 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  22. 2026-10-06 09:50 UTCGHSA enrichmentGHSA-2p8w-fgw9-p46c
  23. 2026-10-06 09:28 UTCNVD update
  24. 2026-10-06 08:55 UTCEG score recompute
  25. 2026-10-06 08:52 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-98216?
CVE-2026-98216 is a high-severity vulnerability; its CVE record was published on October 6, 2026. In the Linux kernel, the following vulnerability has been resolved: IB/hfi1: Fix the PIO_CRED credit-return mmap hfi1filemmap()'s PIO_CRED case must hand user space the single credit-return page that holds this context's entry. That page is the second or third page of the per-node credit-return…
When was the CVE record for CVE-2026-98216 published?
The CVE record for CVE-2026-98216 was published on October 6, 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 7, 2026; the record at its source may have been updated since.
Is CVE-2026-98216 actively exploited?
CVE-2026-98216 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.1% probability of exploitation in the next 30 days (2nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-98216?
CVE-2026-98216 has a CVSS base score of 7.1 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-98216?
A fix for CVE-2026-98216 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-98216 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-98216

Explore →

Is Your Infrastructure Affected by CVE-2026-98216?

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

Book a Demo →Browse All CVEs