CVE-2026-46117

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 — 3 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: Remove user triggerable WARN_ON() in mana_ib_create_qp_rss()

Sashiko points out that the user can specify WQs sharing the same CQ as a part of the uAPI and this will trigger the WARN_ON() then go on to corrupt the kernel.

Just reject it outright and fail the QP creation.

CVSS v3
7.8
EG Score
7.8(medium)
EPSS
3.2%
KEV
Not listed

Published

May 28, 2026

Last Modified

July 21, 2026

Advisory Details (4)

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

RDMA/mana: Remove user triggerable WARN_ON() in mana_ib_create_qp_rss() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/db991ba50087ad99fa12a2c483aa3be19671ea73
generic

RDMA/mana: Remove user triggerable WARN_ON() in mana_ib_create_qp_rss() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/9ef65af26b2a6738bf15812042e84b3112402d3a
generic

RDMA/mana: Remove user triggerable WARN_ON() in mana_ib_create_qp_rss() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/9cc0c6b1ba8cd5c55aef043e1384de0a8b4efa71
generic

RDMA/mana: Remove user triggerable WARN_ON() in mana_ib_create_qp_rss() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/159f2efabc89d3f931d38f2d35876535d4abf0a3

Vendor Advisories for CVE-2026-46117(3)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(2)

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

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(2)

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

Data Freshness Timeline

(refreshed 9× in last 7d / 64× 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 143 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-46117?
CVE-2026-46117 is a high vulnerability published on May 28, 2026. In the Linux kernel, the following vulnerability has been resolved: RDMA/mana: Remove user triggerable WARNON() in manaibcreateqp_rss() Sashiko points out that the user can specify WQs sharing the same CQ as a part of the uAPI and this will trigger the WARN_ON() then go on to corrupt the kernel.…
When was CVE-2026-46117 disclosed?
CVE-2026-46117 was first published in the National Vulnerability Database on May 28, 2026, with the most recent update on July 21, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-46117 actively exploited?
CVE-2026-46117 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 3.2% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-46117?
CVE-2026-46117 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-46117?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-46117, 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-46117

Explore →

Is Your Infrastructure Affected by CVE-2026-46117?

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

Start Free Scan →Browse All CVEs