Review reviewHigh

CVE-2026-46145

Linux Linux, Red Hat Enterprise Linux 10, Red Hat Enterprise Linux 8

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
7.8
EPSS
0.14%
3.95% percentile
CISA KEV
Not listed
Published
2026.05.28
PRIORITY ASSESSMENT

Review review

The CVSS severity warrants an early asset and exposure review.

Known exploitationNot established by KEV
Exploit probability0.14%
Technical severityCVSS 7.8

Vulnerability overview

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.

Affected product and versions

Product
Linux Linux, Red Hat Enterprise Linux 10, Red Hat Enterprise Linux 8
Affected versions
>= 0266a177631d4c6b963b5b12dd986a8c5abdbf06 < 7d7c9f0fcd19c4d2f0164347c58d49cafa961b72, >= 0266a177631d4c6b963b5b12dd986a8c5abdbf06 < 11c1431d641e0e4e0529e96957995820600c7287, >= 0266a177631d4c6b963b5b12dd986a8c5abdbf06 < 012796f9541fcd0c1fa8ae4da7eb4d83931ef838, >= 0266a177631d4c6b963b5b12dd986a8c5abdbf06 < 7d94f155f354b961c598f71bafa804dceded513f, >= 0266a177631d4c6b963b5b12dd986a8c5abdbf06 < 6dd2d4ad9c8429523b1c220c5132bd551c006425, >= 6.2, >= 6.2 < 6.6.141, >= 6.7 < 6.12.88, >= 6.13 < 6.18.30, >= 6.19 < 7.0.7, 7.1
Fixed versions
6.6.141, 6.12.88, 6.18.30, 7.0.7

Recommended response sequence

Confirm exposure before applying a vendor-supported change.

Full remediation guide
  1. 1
    Identify

    Confirm that Linux Linux, Red Hat Enterprise Linux 10, Red Hat Enterprise Linux 8 and an affected version are present.

  2. 2
    Prioritize

    Combine exploitation signals with asset exposure and business criticality.

  3. 3
    Remediate

    Follow the vendor advisory or supported update path and preserve rollback options.

  4. 4
    Verify

    Recheck the version, service health, access paths, and relevant logs.

Technical data

CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
CWE
CWE-787