From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-72498: RDMA/bnxt_re: Avoid displaying the kernel pointer
Date: Sat, 15 Aug 2026 15:09:37 +0900 [thread overview]
Message-ID: <2026081540-CVE-2026-72498-44af@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
RDMA/bnxt_re: Avoid displaying the kernel pointer
While dumping the info on MR using the rdma tool, we
dump the mr_hwq which is a kernel pointer. There is
no need to expose this value for end user. So avoid
it.
The Linux kernel CVE team has assigned CVE-2026-72498 to this issue.
Affected and fixed versions
===========================
Issue introduced in 6.13 with commit 7363eb76b7f3b860ecfb8fcaf537e143bfd725bd and fixed in 6.18.40 with commit 95d46a8d3ba9fdbe356fe7ed0117bc78dac9d557
Issue introduced in 6.13 with commit 7363eb76b7f3b860ecfb8fcaf537e143bfd725bd and fixed in 7.1.5 with commit 0c403e0786768d88cabe0ccf4e45425da2fd8841
Issue introduced in 6.13 with commit 7363eb76b7f3b860ecfb8fcaf537e143bfd725bd and fixed in 7.2-rc1 with commit 7d70c704a06f620d5d421ab76bac5e225bfb4308
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-72498
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/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/95d46a8d3ba9fdbe356fe7ed0117bc78dac9d557
https://git.kernel.org/stable/c/0c403e0786768d88cabe0ccf4e45425da2fd8841
https://git.kernel.org/stable/c/7d70c704a06f620d5d421ab76bac5e225bfb4308
reply other threads:[~2026-08-15 6:32 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=2026081540-CVE-2026-72498-44af@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.