From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-46181: RDMA/mlx4: Fix mis-use of RCU in mlx4_srq_event()
Date: Thu, 28 May 2026 11:37:26 +0200 [thread overview]
Message-ID: <2026052829-CVE-2026-46181-ecff@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
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.
The Linux kernel CVE team has assigned CVE-2026-46181 to this issue.
Affected and fixed versions
===========================
Issue introduced in 4.9 with commit 30353bfc43a1602c020f31d95cf27182ffd23824 and fixed in 6.18.30 with commit 1e2a44875b6afb4add1115f7f3351dcbeb6f273d
Issue introduced in 4.9 with commit 30353bfc43a1602c020f31d95cf27182ffd23824 and fixed in 7.0.7 with commit 8b7833f3bce35cb0d01c1503781523c099c675f0
Issue introduced in 4.9 with commit 30353bfc43a1602c020f31d95cf27182ffd23824 and fixed in 7.1-rc3 with commit c9341307ea16b9395c2e4c9c94d8499d91fe31d0
Please see https://www.kernel.org for a full list of currently supported
kernel versions by the kernel community.
Unaffected versions might change over time as fixes are backported to
older supported kernel versions. The official CVE entry at
https://cve.org/CVERecord/?id=CVE-2026-46181
will be updated if fixes are backported, please check that for the most
up to date information about this issue.
Affected files
==============
The file(s) affected by this issue are:
drivers/net/ethernet/mellanox/mlx4/srq.c
Mitigation
==========
The Linux kernel CVE team recommends that you update to the latest
stable kernel version for this, and many other bugfixes. Individual
changes are never tested alone, but rather are part of a larger kernel
release. Cherry-picking individual commits is not recommended or
supported by the Linux kernel community at all. If however, updating to
the latest release is impossible, the individual changes to resolve this
issue can be found at these commits:
https://git.kernel.org/stable/c/1e2a44875b6afb4add1115f7f3351dcbeb6f273d
https://git.kernel.org/stable/c/8b7833f3bce35cb0d01c1503781523c099c675f0
https://git.kernel.org/stable/c/c9341307ea16b9395c2e4c9c94d8499d91fe31d0
reply other threads:[~2026-05-28 9:42 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2026052829-CVE-2026-46181-ecff@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=cve@kernel.org \
--cc=gregkh@kernel.org \
--cc=linux-cve-announce@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.