Menu

Star on GitHub · 3.4k

CVE-2026-98216

7.1 · HIGH

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 pag…

Published Oct 6, 2026EPSS 0.13%

Overview

CVE-2026-98216 is a high-severity vulnerability. It was published on October 6, 2026 and has a CVSS 3.1 base score of 7.1 (HIGH).

This vulnerability has a CVSS 3.1 base score of 7.1, rated HIGH. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.

Technical description

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.

Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

Frequently asked questions

What is CVE-2026-98216?

CVE-2026-98216 is a high-severity vulnerability. It was published on October 6, 2026 and has a CVSS 3.1 base score of 7.1 (HIGH).

How severe is CVE-2026-98216?

This vulnerability has a CVSS 3.1 base score of 7.1, rated HIGH. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.

How do I fix or remediate CVE-2026-98216?

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2026-98216?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2026-98216 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.

Related HIGH CVEs from 2026

View all
Watch the demo →