From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-72501: RDMA/bnxt_re: Initialize dpi variable to zero
Date: Sat, 15 Aug 2026 15:09:40 +0900 [thread overview]
Message-ID: <2026081540-CVE-2026-72501-a897@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
RDMA/bnxt_re: Initialize dpi variable to zero
dpi is initialized only for BNXT_RE_ALLOC_WC_PAGE, but copied
for all the cases. So initialize the dpi to 0.
The Linux kernel CVE team has assigned CVE-2026-72501 to this issue.
Affected and fixed versions
===========================
Issue introduced in 6.5 with commit 360da60d6c6edb9740de7a8e6d8969d62ceff956 and fixed in 6.18.40 with commit b87cbd4d198ae377be4815d8102fa9dfefb91dcc
Issue introduced in 6.5 with commit 360da60d6c6edb9740de7a8e6d8969d62ceff956 and fixed in 7.1.5 with commit 3d00b375853fbbf4157ad092884b4ed9a49429c1
Issue introduced in 6.5 with commit 360da60d6c6edb9740de7a8e6d8969d62ceff956 and fixed in 7.2-rc1 with commit 978b27d6ce538bb832ccd69e45802824e4301c4b
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-72501
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/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/b87cbd4d198ae377be4815d8102fa9dfefb91dcc
https://git.kernel.org/stable/c/3d00b375853fbbf4157ad092884b4ed9a49429c1
https://git.kernel.org/stable/c/978b27d6ce538bb832ccd69e45802824e4301c4b
reply other threads:[~2026-08-15 6:33 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-72501-a897@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