CVE-2026-97421

Received Received - Intake

RDMA Memory Corruption in Linux Kernel

Publication date: 2026-09-24

Last updated on: 2026-10-03

Assigner: kernel.org

Description

In the Linux kernel, the following vulnerability has been resolved: RDMA/umem: Be careful about boundary conditions in ib_umem_find_best_pgsz() Several corner cases, especially important on 32 bits: - umem->iova is u64, the function argument should pass in u64 or iova will be truncated - Check that the length is not too large for the iova - Check that lengths > 4G don't overflow the GENMASK

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published

2026-09-24

Last Modified

2026-10-03

Generated

2026-10-15

AI Q&A

2026-09-24

EPSS Evaluated

2026-10-13

NVD

CVE-2026-97421

EUVD

EUVD-2026-86034

Affected Vendors & Products

Vendor	Product	Version / Range
linux	linux_kernel	*

Helpful Resources

Exploitability

CWE

KEV

CWE ID	Description
CWE-UNKNOWN

Attack-Flow Graph

Executive Summary

This vulnerability in the Linux kernel involves boundary condition issues in the function ib_umem_find_best_pgsz(). It affects 32-bit systems where the iova (input/output virtual address) could be truncated if passed as a 32-bit value instead of a 64-bit value. Additionally, it checks for potential overflows when handling lengths greater than 4GB.

Detection Guidance

This vulnerability is specific to the Linux kernel's RDMA/umem subsystem and involves boundary conditions in ib_umem_find_best_pgsz(). Detection requires checking if your kernel version includes the vulnerable function and verifying if the described corner cases are present. No direct commands are provided in the context to detect this issue.

Impact Analysis

On 32-bit systems, this vulnerability could lead to memory corruption or crashes due to incorrect handling of large memory regions. It may cause instability or denial of service if exploited maliciously.

Compliance Impact

This vulnerability does not directly affect compliance with GDPR, HIPAA, or similar standards as it is a low-level kernel memory management issue without documented impact on data protection or privacy controls.

Mitigation Strategies

Immediate mitigation involves updating the Linux kernel to a version that resolves this vulnerability. Since the issue is in the kernel's RDMA subsystem, applying the latest stable kernel update is recommended. No specific commands are provided in the context for mitigation.

Hi! I’m here to help you understand CVE-2026-97421. Ask me anything about the vulnerability, its impact, or mitigation strategies.

0/70