From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-72500: RDMA/bnxt_re: Free SRQ toggle page after firmware teardown
Date: Sat, 15 Aug 2026 15:09:39 +0900 [thread overview]
Message-ID: <2026081540-CVE-2026-72500-b888@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
RDMA/bnxt_re: Free SRQ toggle page after firmware teardown
Free the toggle page only after firmware teardown completes so that
an NQ interrupt arriving during bnxt_qplib_destroy_srq() won't write
the toggle values to an already-freed page. Move free_page() after
bnxt_qplib_destroy_srq().
The Linux kernel CVE team has assigned CVE-2026-72500 to this issue.
Affected and fixed versions
===========================
Issue introduced in 6.12 with commit 181028a0d84cdcc7ac86d05cc49eaa416ce85c8b and fixed in 6.18.40 with commit 104a7ff382a58a83cae018925e3574c784e8274c
Issue introduced in 6.12 with commit 181028a0d84cdcc7ac86d05cc49eaa416ce85c8b and fixed in 7.1.5 with commit 0adcd67f3d6f84835be682da0153f57f5c2f8036
Issue introduced in 6.12 with commit 181028a0d84cdcc7ac86d05cc49eaa416ce85c8b and fixed in 7.2-rc1 with commit 131e2918b9b0529687e67e2e58047304027f095a
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-72500
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
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/104a7ff382a58a83cae018925e3574c784e8274c
https://git.kernel.org/stable/c/0adcd67f3d6f84835be682da0153f57f5c2f8036
https://git.kernel.org/stable/c/131e2918b9b0529687e67e2e58047304027f095a
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-72500-b888@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