0.0
NA
CVE-2026-46181
RDMA/mlx4: Fix mis-use of RCU in mlx4_srq_event()
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.

INFO

Published Date :

May 28, 2026, 10:16 a.m.

Last Modified :

May 28, 2026, 10:16 a.m.

Remotely Exploit :

No

Source :

416baaa9-dc9f-4396-8d5f-8c081fb06d67
Affected Products

The following products are affected by CVE-2026-46181 vulnerability. Even if cvefeed.io is aware of the exact versions of the products that are affected, the information is not represented in the table below.

No affected product recoded yet

Solution
Apply kernel updates to fix RCU mis-use and protect against partially initialized objects.
  • Apply the Linux kernel security update.
  • Verify RCU usage and refcount synchronization.
  • Ensure SRQ objects initialize fully before use.
  • Order refcount set after SRQ initialization.
References to Advisories, Solutions, and Tools

Here, you will find a curated list of external links that provide in-depth information, practical solutions, and valuable tools related to CVE-2026-46181.

URL Resource
https://git.kernel.org/stable/c/1e2a44875b6afb4add1115f7f3351dcbeb6f273d
https://git.kernel.org/stable/c/8b7833f3bce35cb0d01c1503781523c099c675f0
https://git.kernel.org/stable/c/c9341307ea16b9395c2e4c9c94d8499d91fe31d0
CWE - Common Weakness Enumeration

While CVE identifies specific instances of vulnerabilities, CWE categorizes the common flaws or weaknesses that can lead to vulnerabilities. CVE-2026-46181 is associated with the following CWEs:

Common Attack Pattern Enumeration and Classification (CAPEC)

Common Attack Pattern Enumeration and Classification (CAPEC) stores attack patterns, which are descriptions of the common attributes and approaches employed by adversaries to exploit the CVE-2026-46181 weaknesses.

We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).

Results are limited to the first 15 repositories due to potential performance issues.

The following list is the news that have been mention CVE-2026-46181 vulnerability anywhere in the article.

The following table lists the changes that have been made to the CVE-2026-46181 vulnerability over time.

Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.

  • New CVE Received by 416baaa9-dc9f-4396-8d5f-8c081fb06d67

    May. 28, 2026

    Action Type Old Value New Value
    Added 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.
    Added Reference https://git.kernel.org/stable/c/1e2a44875b6afb4add1115f7f3351dcbeb6f273d
    Added Reference https://git.kernel.org/stable/c/8b7833f3bce35cb0d01c1503781523c099c675f0
    Added Reference https://git.kernel.org/stable/c/c9341307ea16b9395c2e4c9c94d8499d91fe31d0
EPSS is a daily estimate of the probability of exploitation activity being observed over the next 30 days. Following chart shows the EPSS score history of the vulnerability.