CVE-2026-46176

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/mlx5: Fix error path fall-through in mlx5_ib_dev_res_srq_init()

mlx5_ib_dev_res_srq_init() allocates two SRQs, s0 and s1. When ib_create_srq() fails for s1, the error branch destroys s0 but falls through and unconditionally assigns the freed s0 and the ERR_PTR s1 to devr->s0 and devr->s1.

This leads to several problems: the lock-free fast path checks "if (devr->s1) return 0;" and treats the ERR_PTR as already initialised; users in mlx5_ib_create_qp() dereference the freed SRQ or ERR_PTR via to_msrq(devr->s0)->msrq.srqn; and mlx5_ib_dev_res_cleanup() dereferences the ERR_PTR and double-frees s0 on teardown.

Fix by adding the same goto unlock in the s1 failure path.

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/mlx5: Fix error path fall-through in mlx5_ib_dev_res_srq_init() - kernel/git/stable/linux.git - Linux kernel stable tree

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

RDMA/mlx5: Fix error path fall-through in mlx5_ib_dev_res_srq_init() - kernel/git/stable/linux.git - Linux kernel stable tree

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

RDMA/mlx5: Fix error path fall-through in mlx5_ib_dev_res_srq_init() - kernel/git/stable/linux.git - Linux kernel stable tree

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

RDMA/mlx5: Fix error path fall-through in mlx5_ib_dev_res_srq_init() - kernel/git/stable/linux.git - Linux kernel stable tree

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

RDMA/mlx5: Fix error path fall-through in mlx5_ib_dev_res_srq_init() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/6fd93142dd1d09000c3750af08270f5792523fe9

Vendor Advisories for CVE-2026-46176(6)

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

Patch Availability(4)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatkernel-0:5.14.0-570.125.1.el9_62026-07-01redhat
redhatkernel-0:6.12.0-211.29.1.el10_22026-06-30redhat
redhatkernel-0:5.14.0-687.19.1.el9_82026-06-29redhat
redhatkernel-0:6.12.0-55.84.1.el10_02026-06-29redhat

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

Frequently asked(5)

What is CVE-2026-46176?
CVE-2026-46176 is a high vulnerability published on May 28, 2026. In the Linux kernel, the following vulnerability has been resolved: RDMA/mlx5: Fix error path fall-through in mlx5ibdevressrq_init() mlx5ibdevressrq_init() allocates two SRQs, s0 and s1. When ibcreatesrq() fails for s1, the error branch destroys s0 but falls through and unconditionally assigns the…
When was CVE-2026-46176 disclosed?
CVE-2026-46176 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-46176 actively exploited?
CVE-2026-46176 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-46176?
CVE-2026-46176 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-46176?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-46176, 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-46176

Explore →

Is Your Infrastructure Affected by CVE-2026-46176?

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

Start Free Scan →Browse All CVEs