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
7.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.8Exploit: None knownExposed: 0

A fix is available — apply it.

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)
EG Risk
40(Track)
EG Risk 40/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity78% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
3%
KEV
Not listed

Published

May 28, 2026

Last Modified

August 5, 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.

Affected Packages

(5 across 4 ecosystems)
Debian:11(2)
PackageVulnerable rangeFixed inDependents
linux5.10.103-1 ... 5.10.92-2 (54 versions)5.10.259-1
linux-6.16.1.106-3~deb11u1 ... 6.1.174-1~deb11u1 (20 versions)6.1.176-1~deb11u1
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 6.1.99-1 (53 versions)6.1.176-1
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.88-1~bpo12+1 (21 versions)6.12.88-1
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.0.7-1~bpo13+1 (133 versions)7.0.7-1

Weakness Classification(1)

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

Additional Vendor Advisories

(24)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 5× in last 7d / 85× 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 281 total refreshes for this CVE.

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

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 August 5, 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 0% probability of exploitation in the next 30 days, which ranks it in the top 97.1% of all scored CVEs.
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

See which npm, PyPI, Go, and Maven packages are affected by 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.