From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-72495: RDMA/bnxt_re: Avoid repeated requests to allocate WC pages
Date: Sat, 15 Aug 2026 15:09:34 +0900 [thread overview]
Message-ID: <2026081539-CVE-2026-72495-d1ba@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
RDMA/bnxt_re: Avoid repeated requests to allocate WC pages
Applications can request multiple WC pages for the same ucontext.
As of now, only 1 WC page per ucontext is supported. Add a lock to
avoid concurrent access and a check to fail repeated requests.
Also, if the mmap entry insert fails for the WC, free the Doorbell
page index mapped for the WC page.
The Linux kernel CVE team has assigned CVE-2026-72495 to this issue.
Affected and fixed versions
===========================
Issue introduced in 6.5 with commit 360da60d6c6edb9740de7a8e6d8969d62ceff956 and fixed in 6.18.40 with commit 478c4d24193fe3e6aa2accd4874ae43000e4a217
Issue introduced in 6.5 with commit 360da60d6c6edb9740de7a8e6d8969d62ceff956 and fixed in 7.1.5 with commit da406b8b49c1dfe661a497483940d7ee781430db
Issue introduced in 6.5 with commit 360da60d6c6edb9740de7a8e6d8969d62ceff956 and fixed in 7.2-rc1 with commit 441baa79043431807115fd030d7d0bb14ed441a0
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-72495
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/bnxt_re/ib_verbs.c
drivers/infiniband/hw/bnxt_re/ib_verbs.h
drivers/infiniband/hw/bnxt_re/uapi.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/478c4d24193fe3e6aa2accd4874ae43000e4a217
https://git.kernel.org/stable/c/da406b8b49c1dfe661a497483940d7ee781430db
https://git.kernel.org/stable/c/441baa79043431807115fd030d7d0bb14ed441a0
reply other threads:[~2026-08-15 6:31 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=2026081539-CVE-2026-72495-d1ba@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.