CVE-2026-46181

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.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 mis-use of RCU in mlx4_srq_event()

Sashiko points out the radix_tree itself is RCU safe, but nothing ever frees the mlx4_srq struct with RCU, and it isn't even accessed within the RCU critical section. It also will crash if an event is delivered before the srq object is finished initializing.

Use the spinlock since it isn't easy to make RCU work, use refcount_inc_not_zero() to protect against partially initialized objects, and order the refcount_set() to be after the srq is fully initialized.

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
2%
KEV
Not listed

Published

May 28, 2026

Last Modified

August 5, 2026

Advisory Details (3)

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

RDMA/mlx4: Fix mis-use of RCU in mlx4_srq_event() - kernel/git/stable/linux.git - Linux kernel stable tree

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

RDMA/mlx4: Fix mis-use of RCU in mlx4_srq_event() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/8b7833f3bce35cb0d01c1503781523c099c675f0
generic

RDMA/mlx4: Fix mis-use of RCU in mlx4_srq_event() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/1e2a44875b6afb4add1115f7f3351dcbeb6f273d

Vendor Advisories for CVE-2026-46181(14)

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

Patch Availability(20)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-tools-oem-7.0 (7.0.0-1009.9) @ resolute2026-08-25ubuntu
ubuntulinux-virtual-hwe-24.04-edge (7.0.0-28.28~24.04.1) @ noble2026-08-25ubuntu
ubuntulinux-tools-oracle-7.0 (7.0.0-1008.8) @ resolute2026-08-25ubuntu
ubuntulinux-tools-nvidia-hwe-26.04 (7.0.0-2016.16) @ resolute2026-08-25ubuntu
ubuntulinux-tools-nvidia-hwe-24.04-edge (7.0.0-1016.16) @ resolute2026-08-25ubuntu
ubuntulinux-tools-raspi-realtime-7.0 (7.0.0-1015.15) @ resolute2026-08-25ubuntu
ubuntulinux-tools-azure-fde-7.0 (7.0.0-1009.9) @ resolute2026-08-25ubuntu
ubuntulinux-virtual-hwe-26.04-edge (7.0.0-28.28) @ resolute2026-08-25ubuntu
redhatkernel-rt-0:3.10.0-1160.155.1.rt56.1307.el72026-07-17redhat
redhatkernel-0:3.10.0-1160.155.1.el72026-07-07redhat
redhatkernel-0:4.18.0-305.197.1.el8_42026-07-06redhat
redhatkernel-0:4.18.0-477.150.1.el8_82026-07-06redhat
redhatkernel-0:4.18.0-372.199.1.el8_62026-07-06redhat
redhatkernel-0:5.14.0-570.125.1.el9_62026-07-01redhat
redhatkernel-0:5.14.0-427.135.1.el9_42026-07-01redhat
redhatkernel-rt-0:5.14.0-284.178.1.rt14.463.el9_22026-07-01redhat
redhatkernel-0:5.14.0-284.178.1.el9_22026-07-01redhat
redhatkernel-0:5.14.0-687.15.1.el9_82026-06-11redhat
redhatkernel-0:4.18.0-553.132.1.el8_102026-06-10redhat
redhatkernel-rt-0:4.18.0-553.132.1.rt7.473.el8_102026-06-10redhat

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

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
linux5.10.103-1 ... 7.2~rc5-1~exp1 (496 versions)——
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 7.2~rc5-1~exp1 (335 versions)——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.2~rc5-1~exp1 (160 versions)——
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

(8)

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 8× in last 7d / 108× 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 272 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-46181?
CVE-2026-46181 is a high vulnerability published on May 28, 2026. In the Linux kernel, the following vulnerability has been resolved: RDMA/mlx4: Fix mis-use of RCU in mlx4srqevent() Sashiko points out the radix_tree itself is RCU safe, but nothing ever frees the mlx4_srq struct with RCU, and it isn't even accessed within the RCU critical section. It also will…
When was CVE-2026-46181 disclosed?
CVE-2026-46181 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-46181 actively exploited?
CVE-2026-46181 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 98.4% of all scored CVEs.
What is the CVSS score of CVE-2026-46181?
CVE-2026-46181 has a CVSS v4.0 base score of 7.8 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-46181?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-46181, 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-46181

Explore →

Is Your Infrastructure Affected by CVE-2026-46181?

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

Start Free Scan →Browse All CVEs