RDMA/mana Memory Corruption via rx_hash_key_len Validation Bypass

Publication date: 2026-05-28

Last updated on: 2026-06-30

Assigner: kernel.org

Description

In the Linux kernel, the following vulnerability has been resolved: RDMA/mana: Validate rx_hash_key_len Sashiko points out that rx_hash_key_len comes from a uAPI structure and is blindly passed to memcpy, allowing the userspace to trash kernel memory. Bounds check it so the memcpy cannot overflow.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published

2026-05-28

Last Modified

2026-06-30

Generated

2026-07-08

AI Q&A

2026-05-28

EPSS Evaluated

2026-07-06

NVD

CVE-2026-46145

EUVD

EUVD-2026-32772

Affected Vendors & Products

Vendor	Product	Version / Range
linux	linux_kernel	7.1
linux	linux_kernel	7.1
linux	linux_kernel	From 6.13 (inc) to 6.18.30 (exc)
linux	linux_kernel	From 6.2 (inc) to 6.6.141 (exc)
linux	linux_kernel	From 6.19 (inc) to 7.0.7 (exc)
linux	linux_kernel	From 6.7 (inc) to 6.12.88 (exc)

Helpful Resources

Exploitability

CWE

KEV

CWE ID	Description
CWE-787	The product writes data past the end, or before the beginning, of the intended buffer.

Attack-Flow Graph

Executive Summary

This vulnerability exists in the Linux kernel within the RDMA/mana component. It involves the rx_hash_key_len value, which is taken from a user API structure and used without proper validation in a memcpy operation. Because rx_hash_key_len is not checked for bounds, a malicious user can cause the memcpy to overflow, potentially overwriting kernel memory.

Impact Analysis

The vulnerability allows userspace to overwrite kernel memory by exploiting the unchecked length parameter in memcpy. This can lead to memory corruption, which may cause system instability, crashes, or potentially allow an attacker to execute arbitrary code with kernel privileges.

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

0/70