From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-74296: RDMA/mlx5: Release the HW‑provided UAR index rather than the SW one
Date: Sat, 15 Aug 2026 15:10:23 +0900 [thread overview]
Message-ID: <2026081549-CVE-2026-74296-457e@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
RDMA/mlx5: Release the HW‑provided UAR index rather than the SW one
Free the UAR index returned by the hardware.
The Linux kernel CVE team has assigned CVE-2026-74296 to this issue.
Affected and fixed versions
===========================
Issue introduced in 4.16 with commit 4ed131d0bb1597ce12fff22d9d7fc9720a6e8cf0 and fixed in 6.1.178 with commit 80f1f49f53a42733e60c90e0ec545e647969214d
Issue introduced in 4.16 with commit 4ed131d0bb1597ce12fff22d9d7fc9720a6e8cf0 and fixed in 6.6.145 with commit aabfc845838ef453f1d22d7665596f9cc48be7dd
Issue introduced in 4.16 with commit 4ed131d0bb1597ce12fff22d9d7fc9720a6e8cf0 and fixed in 6.12.97 with commit 6f83de384ca582fa87b4c2b0d03bd1ed3bf9a2ee
Issue introduced in 4.16 with commit 4ed131d0bb1597ce12fff22d9d7fc9720a6e8cf0 and fixed in 6.18.40 with commit d3ff718c0c7153e2641e6a09507bace14fc5c402
Issue introduced in 4.16 with commit 4ed131d0bb1597ce12fff22d9d7fc9720a6e8cf0 and fixed in 7.1.5 with commit ef369446f62903ea079e8a7954b5bf8bb8300fe3
Issue introduced in 4.16 with commit 4ed131d0bb1597ce12fff22d9d7fc9720a6e8cf0 and fixed in 7.2-rc1 with commit 449ae7927152e46acbe5f19f97eafdae6d3a96b1
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-74296
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/infiniband/hw/mlx5/main.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/80f1f49f53a42733e60c90e0ec545e647969214d
https://git.kernel.org/stable/c/aabfc845838ef453f1d22d7665596f9cc48be7dd
https://git.kernel.org/stable/c/6f83de384ca582fa87b4c2b0d03bd1ed3bf9a2ee
https://git.kernel.org/stable/c/d3ff718c0c7153e2641e6a09507bace14fc5c402
https://git.kernel.org/stable/c/ef369446f62903ea079e8a7954b5bf8bb8300fe3
https://git.kernel.org/stable/c/449ae7927152e46acbe5f19f97eafdae6d3a96b1
reply other threads:[~2026-08-15 6:35 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=2026081549-CVE-2026-74296-457e@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox