CVE-2026-46181

RDMA/mlx4: Fix mis-use of RCU in mlx4_srq_event()

HIGH
7.8
CVSS Score
Published: May 28, 2026 at 09:36 AM UTC
Updated: October 21, 2026 at 01:19 PM UTC
2 products affected across 2 vendorsLinux KernelEnterprise Linux

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH7.8
Exploit prediction
EPSS 0.1%
SSVC
No known exploit

Description

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

4.9 ≤ v < 6.18.306.19 ≤ v < 7.0.730353bfc43a1602c020f31d95cf27182ffd238247.17.1 rc17.1 rc2
Vendor states this is fixed in 1e2a44875b6afb4add1115f7f3351dcbeb6f273d (fixed)
Vendor states this is fixed in 8b7833f3bce35cb0d01c1503781523c099c675f0 (fixed)
Vendor states this is fixed in c9341307ea16b9395c2e4c9c94d8499d91fe31d0 (fixed)
Vendor states this is fixed in 4.9 (unaffected)
Vendor states this is fixed in 6.12.114 (unaffected)
Vendor states this is fixed in 6.18.30 (unaffected)
Vendor states this is fixed in 6.6.160 (unaffected)
Vendor states this is fixed in 7.0.7 (unaffected)
Vendor states this is fixed in 7.1 (unaffected)
Vendor states this is fixed in 0:3.10.0-1160.155.1.el7 (unaffected)
Vendor states this is fixed in 0:3.10.0-1160.155.1.rt56.1307.el7 (unaffected)
Vendor states this is fixed in 0:4.18.0-305.197.1.el8_4 (unaffected)
Vendor states this is fixed in 0:4.18.0-372.199.1.el8_6 (unaffected)
Vendor states this is fixed in 0:4.18.0-477.150.1.el8_8 (unaffected)
Vendor states this is fixed in 0:4.18.0-553.132.1.el8_10 (unaffected)
Vendor states this is fixed in 0:4.18.0-553.132.1.rt7.473.el8_10 (unaffected)
Vendor states this is fixed in 0:5.14.0-284.178.1.el9_2 (unaffected)
Vendor states this is fixed in 0:5.14.0-284.178.1.rt14.463.el9_2 (unaffected)
Vendor states this is fixed in 0:5.14.0-427.135.1.el9_4 (unaffected)
Vendor states this is fixed in 0:5.14.0-570.125.1.el9_6 (unaffected)
Vendor states this is fixed in 0:5.14.0-687.15.1.el9_8 (unaffected)
Vendor states this is fixed in 10 (unaffected)
Vendor states this is fixed in 6 (unknown)

References (20)

SSVC — Action Prioritization

SSVCNo known exploitNot automatableTotal impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

7.8HIGHLinux
Vector?

Quick Info

StatusMODIFIED
CWE
NVD-CWE-noinfoCWE-366

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card