CVE-2026-46178

HIGHPre-NVD 7.87.8—
EchelonGraph scoreMEDIUM confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-05-28. the CNA's CVSS baseline 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cna:linux, epss, ghsa
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

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

In the Linux kernel, the following vulnerability has been resolved:

RDMA/mlx4: Fix resource leak on error in mlx4_ib_create_srq()

Sashiko points out that mlx4_srq_alloc() was not undone during error unwind, add the missing call to mlx4_srq_free().

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

Published

May 28, 2026

Last Modified

June 14, 2026

Advisory Details (8)

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

RDMA/mlx4: Fix resource leak on error in mlx4_ib_create_srq() - kernel/git/stable/linux.git - Linux kernel stable tree

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

RDMA/mlx4: Fix resource leak on error in mlx4_ib_create_srq() - kernel/git/stable/linux.git - Linux kernel stable tree

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

RDMA/mlx4: Fix resource leak on error in mlx4_ib_create_srq() - kernel/git/stable/linux.git - Linux kernel stable tree

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

RDMA/mlx4: Fix resource leak on error in mlx4_ib_create_srq() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/5b3b220d54e6a3d77380cb7caa1ef79cb8f4fc94
generic

RDMA/mlx4: Fix resource leak on error in mlx4_ib_create_srq() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/53fd4c03558672ccb167754fbacbf045c7ab335c
generic

RDMA/mlx4: Fix resource leak on error in mlx4_ib_create_srq() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/388617f44d81604a760742a0b5de292d411e63e3
generic

RDMA/mlx4: Fix resource leak on error in mlx4_ib_create_srq() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/0dbd619716fb07b7de1acd64fec673ee6e1adde7
generic

RDMA/mlx4: Fix resource leak on error in mlx4_ib_create_srq() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/0be6ae614ca7fa53e7389e3c7462ed20abbd4192

Vendor Advisories for CVE-2026-46178(2)

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

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 12× in last 7d / 86× 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 190 total refreshes for this CVE.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-46178?
CVE-2026-46178 is a high vulnerability published on May 28, 2026. In the Linux kernel, the following vulnerability has been resolved: RDMA/mlx4: Fix resource leak on error in mlx4ibcreate_srq() Sashiko points out that mlx4srqalloc() was not undone during error unwind, add the missing call to mlx4srqfree().
When was CVE-2026-46178 disclosed?
CVE-2026-46178 was first published in the National Vulnerability Database on May 28, 2026, with the most recent update on June 14, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-46178 actively exploited?
CVE-2026-46178 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 2.9% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-46178?
CVE-2026-46178 has a CVSS v4.0 base score of 7.8 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-46178?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-46178, 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-46178

Explore →

Is Your Infrastructure Affected by CVE-2026-46178?

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

Start Free Scan →Browse All CVEs