CVE-2026-46145

HIGHPre-NVD 7.87.8
EchelonGraph scoreMEDIUM confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-05-28. a secondary CVSS source baseline 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
7.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.8Exploit: NoneExposed: 0

A fix is available — apply it.

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 v3
7.8
EG Score
7.8(medium)
EPSS
3.9%
KEV
Not listed

Published

May 28, 2026

Last Modified

July 15, 2026

Advisory Details (5)

Auto-updated Jun 3, 2026
No patch confirmed yet.
generic

RDMA/mana: Validate rx_hash_key_len - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/7d94f155f354b961c598f71bafa804dceded513f
generic

RDMA/mana: Validate rx_hash_key_len - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/7d7c9f0fcd19c4d2f0164347c58d49cafa961b72
generic

RDMA/mana: Validate rx_hash_key_len - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/6dd2d4ad9c8429523b1c220c5132bd551c006425
generic

RDMA/mana: Validate rx_hash_key_len - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/11c1431d641e0e4e0529e96957995820600c7287
generic

RDMA/mana: Validate rx_hash_key_len - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/012796f9541fcd0c1fa8ae4da7eb4d83931ef838

Patch Availability(4)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatkernel-0:6.12.0-211.28.1.el10_22026-06-25redhat
redhatkernel-0:5.14.0-687.17.1.el9_82026-06-22redhat
redhatkernel-rt-0:4.18.0-553.136.1.rt7.477.el8_102026-06-19redhat
redhatkernel-0:4.18.0-553.136.1.el8_102026-06-19redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 13× in last 7d / 88× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 185 total refreshes for this CVE.

  1. 2026-07-16 10:25 UTCEG score recompute
  2. 2026-07-16 10:25 UTCVendor advisory
  3. 2026-07-16 10:25 UTCGHSA enrichment
  4. 2026-07-15 16:57 UTCEPSS rescore
  5. 2026-07-15 02:00 UTCEPSS rescore
  6. 2026-07-13 22:30 UTCEPSS rescore
  7. 2026-07-13 06:13 UTCEPSS rescore
  8. 2026-07-12 05:46 UTCEPSS rescore
  9. 2026-07-11 21:20 UTCEG score recompute
  10. 2026-07-11 21:20 UTCVendor advisory
  11. 2026-07-11 21:20 UTCGHSA enrichment
  12. 2026-07-11 08:27 UTCEPSS rescore
  13. 2026-07-09 19:10 UTCEPSS rescore
  14. 2026-07-08 18:32 UTCEG score recompute
  15. 2026-07-08 18:32 UTCVendor advisory
  16. 2026-07-08 18:32 UTCGHSA enrichment
  17. 2026-07-08 15:16 UTCEPSS rescore
  18. 2026-07-07 13:46 UTCEPSS rescore
  19. 2026-07-05 02:30 UTCEPSS rescore
  20. 2026-07-04 06:31 UTCEPSS rescore
  21. 2026-07-02 14:17 UTCEG score recompute
  22. 2026-07-02 14:17 UTCVendor advisory
  23. 2026-07-02 14:17 UTCGHSA enrichment
  24. 2026-07-01 16:50 UTCEG score recompute
  25. 2026-07-01 16:50 UTCVendor advisory
Show 75 more
  1. 2026-07-01 16:50 UTCGHSA enrichment
  2. 2026-07-01 15:07 UTCEPSS rescore
  3. 2026-07-01 03:12 UTCEG score recompute
  4. 2026-07-01 03:12 UTCVendor advisory
  5. 2026-07-01 03:12 UTCGHSA enrichment
  6. 2026-06-30 23:22 UTCEPSS rescore
  7. 2026-06-30 03:08 UTCEG score recompute
  8. 2026-06-30 03:08 UTCVendor advisory
  9. 2026-06-30 03:08 UTCGHSA enrichment
  10. 2026-06-29 14:06 UTCEPSS rescore
  11. 2026-06-29 14:06 UTCEPSS rescore
  12. 2026-06-29 13:45 UTCEG score recompute
  13. 2026-06-29 13:45 UTCVendor advisory
  14. 2026-06-29 13:45 UTCGHSA enrichment
  15. 2026-06-28 21:29 UTCEG score recompute
  16. 2026-06-28 21:29 UTCVendor advisory
  17. 2026-06-28 21:29 UTCGHSA enrichment
  18. 2026-06-28 14:07 UTCEPSS rescore
  19. 2026-06-28 08:20 UTCEG score recompute
  20. 2026-06-28 08:20 UTCVendor advisory
  21. 2026-06-28 08:20 UTCGHSA enrichment
  22. 2026-06-28 04:56 UTCEPSS rescore
  23. 2026-06-28 04:56 UTCEPSS rescore
  24. 2026-06-27 19:09 UTCEG score recompute
  25. 2026-06-27 19:09 UTCVendor advisory
  26. 2026-06-27 19:09 UTCGHSA enrichment
  27. 2026-06-27 06:01 UTCEG score recompute
  28. 2026-06-27 06:01 UTCVendor advisory
  29. 2026-06-27 06:01 UTCGHSA enrichment
  30. 2026-06-27 03:08 UTCEPSS rescore
  31. 2026-06-26 16:53 UTCEG score recompute
  32. 2026-06-26 16:53 UTCVendor advisory
  33. 2026-06-26 16:52 UTCGHSA enrichment
  34. 2026-06-26 02:06 UTCEG score recompute
  35. 2026-06-26 02:06 UTCVendor advisory
  36. 2026-06-26 02:06 UTCGHSA enrichment
  37. 2026-06-25 13:49 UTCEPSS rescore
  38. 2026-06-25 12:00 UTCEG score recompute
  39. 2026-06-25 12:00 UTCVendor advisory
  40. 2026-06-25 12:00 UTCGHSA enrichment
  41. 2026-06-24 22:49 UTCEG score recompute
  42. 2026-06-24 22:49 UTCVendor advisory
  43. 2026-06-24 22:49 UTCGHSA enrichment
  44. 2026-06-24 14:05 UTCEPSS rescore
  45. 2026-06-23 21:33 UTCEPSS rescore
  46. 2026-06-23 21:33 UTCEPSS rescore
  47. 2026-06-22 14:25 UTCEPSS rescore
  48. 2026-06-22 14:25 UTCEPSS rescore
  49. 2026-06-21 01:59 UTCEPSS rescore
  50. 2026-06-21 01:59 UTCEPSS rescore
  51. 2026-06-19 19:26 UTCEPSS rescore
  52. 2026-06-19 19:26 UTCEPSS rescore
  53. 2026-06-18 17:52 UTCEPSS rescore
  54. 2026-06-18 17:52 UTCEPSS rescore
  55. 2026-06-17 18:15 UTCEG score recompute
  56. 2026-06-17 18:14 UTCGHSA enrichment
  57. 2026-06-17 17:53 UTCEPSS rescore
  58. 2026-06-17 04:51 UTCEG score recompute
  59. 2026-06-17 04:51 UTCGHSA enrichment
  60. 2026-06-16 17:52 UTCEPSS rescore
  61. 2026-06-16 15:44 UTCEG score recompute
  62. 2026-06-16 15:44 UTCVendor advisory
  63. 2026-06-16 15:44 UTCGHSA enrichment
  64. 2026-06-16 02:10 UTCEG score recompute
  65. 2026-06-16 02:10 UTCVendor advisory
  66. 2026-06-16 02:10 UTCGHSA enrichment
  67. 2026-06-15 17:49 UTCEPSS rescore
  68. 2026-06-15 13:03 UTCEG score recompute
  69. 2026-06-15 13:03 UTCVendor advisory
  70. 2026-06-15 13:03 UTCGHSA enrichment
  71. 2026-06-14 21:53 UTCEG score recompute
  72. 2026-06-14 21:53 UTCVendor advisory
  73. 2026-06-14 21:53 UTCGHSA enrichment
  74. 2026-06-14 08:45 UTCEG score recompute
  75. 2026-06-14 08:45 UTCVendor advisory

Frequently asked(5)

What is CVE-2026-46145?
CVE-2026-46145 is a high vulnerability published on May 28, 2026. In the Linux kernel, the following vulnerability has been resolved: RDMA/mana: Validate rxhashkey_len Sashiko points out that rxhashkey_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.
When was CVE-2026-46145 disclosed?
CVE-2026-46145 was first published in the National Vulnerability Database on May 28, 2026, with the most recent update on July 15, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-46145 actively exploited?
CVE-2026-46145 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 3.9% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-46145?
CVE-2026-46145 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-46145?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-46145, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-46145

Explore →

Is Your Infrastructure Affected by CVE-2026-46145?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.