Kernel crash via incorrect PIO credit mapping
Published Oct 6, 2026 · Updated Oct 6, 2026
Improper memory mapping in the hfi1 driver in Linux 6.3 allows local users to crash the kernel through a PIO_CRED mapping. In hfi1_file_mmap(), a byte offset is added to a typed credit_return pointer, while dma_mmap_coherent() receives an offset address after vm_pgoff is reset to zero, selecting an invalid or wrong credit-return page. An affected Omni-Path send context with a translating IOMMU can trigger a kernel Oops on the first read; mapping the wrong page can instead leave send PIO hanging.
Summary
What happened
Improper memory mapping in the hfi1 driver in Linux 6.3 allows local users to crash the kernel through a PIO_CRED mapping. In hfi1_file_mmap(), a byte offset is added to a typed credit_return pointer, while dma_mmap_coherent() receives an offset address after vm_pgoff is reset to zero, selecting an invalid or wrong credit-return page. An affected Omni-Path send context with a translating IOMMU can trigger a kernel Oops on the first read; mapping the wrong page can instead leave send PIO hanging.
The record
- CVE
- CVE-2026-98216
- Published
- Oct 6, 2026
- Updated
- Oct 6, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- T1499.004
- Attack vector
- local
- Privileges
- Unavailable
Timeline
How it unfolded
- Oct 6, 2026CVE publishedPublication date reported by the CVE source.
- Oct 6, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=1ec82317a1daac78c04b0c15af89018ccf9fa2b7 <180752deb7270ad37394ab6ef7cf4978fad040b3
- Affected versionversion=1ec82317a1daac78c04b0c15af89018ccf9fa2b7 <535530bb2ea5254e1e9f55280143d262dd065204
- Affected versionversion=1ec82317a1daac78c04b0c15af89018ccf9fa2b7 <62f0f34fbd2b2d5653d33d3b9d42fdcabb1c0101
- Affected versionversion=1ec82317a1daac78c04b0c15af89018ccf9fa2b7 <bafeac9ce5d1ce5256bcf7e5702e831e9aaf419b
- Affected versionversion=1ec82317a1daac78c04b0c15af89018ccf9fa2b7 <dcebe0b0bb080a25fe08011fd6b6e741f7912f01
- Affected versionversion=6.3
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Activity data is delayed. The latest report is Sep 28, 2026.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Get started