CVE-2026-46176

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/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)
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
4%
KEV
Not listed

Published

May 28, 2026

Last Modified

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

Patch Availability(26)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-tools-aws-fips-6.8 (6.8.0-1061.64+fips1) @ noble2026-08-25ubuntu
ubuntulinux-tools-gcp-fips-6.8 (6.8.0-1064.72+fips1) @ noble2026-08-25ubuntu
ubuntulinux-tools-oem-7.0 (7.0.0-1009.9) @ resolute2026-08-25ubuntu
ubuntulinux-tools-raspi-realtime-6.8 (6.8.0-2050.52) @ noble2026-08-25ubuntu
ubuntulinux-tools-oracle-lts-24.04 (6.8.0-1058.61) @ noble2026-08-25ubuntu
ubuntulinux-tools-oracle-7.0 (7.0.0-1008.8) @ resolute2026-08-25ubuntu
ubuntulinux-tools-oracle-edge (6.8.0-1058.61~22.04.1) @ jammy2026-08-25ubuntu
ubuntulinux-tools-azure-fde-7.0 (7.0.0-1009.9) @ resolute2026-08-25ubuntu
ubuntulinux-tools-aws-lts-24.04 (6.8.0-1061.64+1) @ noble2026-08-25ubuntu
ubuntulinux-virtual-hwe-26.04-edge (7.0.0-28.28) @ resolute2026-08-25ubuntu
ubuntulinux-tools-azure-fde-lts-24.04 (6.8.0-1062.69) @ noble2026-08-25ubuntu
ubuntulinux-tools-azure-fips-6.8 (6.8.0-1063.71+fips2) @ noble2026-08-25ubuntu
ubuntulinux-tools-azure-fde-6.8 (6.8.0-1062.69~22.04.1) @ jammy2026-08-25ubuntu
ubuntulinux-tools-raspi-realtime-7.0 (7.0.0-1015.15) @ resolute2026-08-25ubuntu
ubuntulinux-tools-nvidia-hwe-24.04-edge (7.0.0-1016.16) @ resolute2026-08-25ubuntu
ubuntulinux-tools-nvidia-hwe-26.04 (7.0.0-2016.16) @ resolute2026-08-25ubuntu
ubuntulinux-xilinx-zynqmp (6.8.0.1033.34) @ noble2026-08-25ubuntu
ubuntulinux-virtual-hwe-22.04-edge (6.8.0-136.136~22.04.1) @ jammy2026-08-25ubuntu
ubuntulinux-tools-azure-lts-24.04 (6.8.0-1063.71) @ noble2026-08-25ubuntu
ubuntulinux-tools-nvidia-lowlatency-64k-6.8 (6.8.0-1059.62.1) @ noble2026-08-25ubuntu
ubuntulinux-virtual-6.8 (6.8.0-136.136) @ noble2026-08-25ubuntu
ubuntulinux-virtual-hwe-24.04-edge (7.0.0-28.28~24.04.1) @ noble2026-08-25ubuntu
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.

Affected Packages

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

(20)

Data Freshness Timeline

(refreshed 5× in last 7d / 90× 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 295 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 UTCEG score recompute
  19. 2026-08-21 15:33 UTCVendor advisory
  20. 2026-08-21 15:33 UTCGHSA enrichment
  21. 2026-08-20 22:55 UTCEPSS rescore
  22. 2026-08-20 22:31 UTCVendor advisory
  23. 2026-08-20 22:31 UTCGHSA enrichment
  24. 2026-08-20 10:56 UTCEG score recompute
  25. 2026-08-20 10:56 UTCVendor advisory
Show 75 more
  1. 2026-08-20 10:55 UTCGHSA enrichment
  2. 2026-08-19 17:04 UTCEPSS rescore
  3. 2026-08-18 13:48 UTCEPSS rescore
  4. 2026-08-17 13:47 UTCEPSS rescore
  5. 2026-08-17 08:55 UTCVendor advisory
  6. 2026-08-17 08:55 UTCGHSA enrichment
  7. 2026-08-16 15:11 UTCEG score recompute
  8. 2026-08-16 15:11 UTCVendor advisory
  9. 2026-08-16 15:11 UTCGHSA enrichment
  10. 2026-08-16 14:56 UTCEPSS rescore
  11. 2026-08-16 02:36 UTCEG score recompute
  12. 2026-08-16 02:36 UTCVendor advisory
  13. 2026-08-16 02:36 UTCGHSA enrichment
  14. 2026-08-16 02:14 UTCEPSS rescore
  15. 2026-08-15 01:30 UTCEPSS rescore
  16. 2026-08-14 23:36 UTCVendor advisory
  17. 2026-08-14 23:36 UTCGHSA enrichment
  18. 2026-08-14 12:23 UTCVendor advisory
  19. 2026-08-14 12:23 UTCGHSA enrichment
  20. 2026-08-14 01:11 UTCEG score recompute
  21. 2026-08-14 01:11 UTCVendor advisory
  22. 2026-08-14 01:11 UTCGHSA enrichment
  23. 2026-08-13 22:00 UTCEPSS rescore
  24. 2026-08-13 08:11 UTCVendor advisory
  25. 2026-08-13 08:11 UTCGHSA enrichment
  26. 2026-08-12 20:57 UTCEG score recompute
  27. 2026-08-12 20:57 UTCVendor advisory
  28. 2026-08-12 20:57 UTCGHSA enrichment
  29. 2026-08-12 13:51 UTCEPSS rescore
  30. 2026-08-12 09:45 UTCVendor advisory
  31. 2026-08-12 09:45 UTCGHSA enrichment
  32. 2026-08-11 22:31 UTCEG score recompute
  33. 2026-08-11 22:31 UTCVendor advisory
  34. 2026-08-11 22:31 UTCGHSA enrichment
  35. 2026-08-11 11:19 UTCVendor advisory
  36. 2026-08-11 11:19 UTCGHSA enrichment
  37. 2026-08-11 00:07 UTCEG score recompute
  38. 2026-08-11 00:07 UTCVendor advisory
  39. 2026-08-11 00:06 UTCGHSA enrichment
  40. 2026-08-11 00:00 UTCEPSS rescore
  41. 2026-08-10 06:34 UTCVendor advisory
  42. 2026-08-10 06:34 UTCGHSA enrichment
  43. 2026-08-09 19:22 UTCEG score recompute
  44. 2026-08-09 19:22 UTCVendor advisory
  45. 2026-08-09 19:22 UTCGHSA enrichment
  46. 2026-08-09 13:46 UTCEPSS rescore
  47. 2026-08-09 08:09 UTCVendor advisory
  48. 2026-08-09 08:09 UTCGHSA enrichment
  49. 2026-08-08 20:57 UTCEG score recompute
  50. 2026-08-08 20:57 UTCVendor advisory
  51. 2026-08-08 20:57 UTCGHSA enrichment
  52. 2026-08-08 16:37 UTCEPSS rescore
  53. 2026-08-08 09:44 UTCVendor advisory
  54. 2026-08-08 09:44 UTCGHSA enrichment
  55. 2026-08-07 22:32 UTCEG score recompute
  56. 2026-08-07 22:32 UTCVendor advisory
  57. 2026-08-07 22:32 UTCGHSA enrichment
  58. 2026-08-07 11:19 UTCVendor advisory
  59. 2026-08-07 11:19 UTCGHSA enrichment
  60. 2026-08-07 00:07 UTCEG score recompute
  61. 2026-08-07 00:07 UTCVendor advisory
  62. 2026-08-07 00:07 UTCGHSA enrichment
  63. 2026-08-06 13:47 UTCEPSS rescore
  64. 2026-08-06 12:06 UTCVendor advisory
  65. 2026-08-06 12:05 UTCGHSA enrichment
  66. 2026-08-06 00:53 UTCEG score recompute
  67. 2026-08-06 00:53 UTCVendor advisory
  68. 2026-08-06 00:53 UTCGHSA enrichment
  69. 2026-08-05 19:17 UTCEPSS rescore
  70. 2026-08-05 13:41 UTCEG score recompute
  71. 2026-08-05 13:41 UTCVendor advisory
  72. 2026-08-05 13:41 UTCGHSA enrichment
  73. 2026-08-05 00:00 UTCEG score recompute
  74. 2026-08-05 00:00 UTCVendor advisory
  75. 2026-08-04 23:59 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 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-46176 actively exploited?
CVE-2026-46176 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 96.2% of all scored CVEs.
What is the CVSS score of CVE-2026-46176?
CVE-2026-46176 has a CVSS v4.0 base score of 7.8 (CNA self-assessment; NVD's own analysis pending).
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

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