From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-97574: bnxt_en: Don't free the live ring's TPA state on queue restart failure
Date: Fri, 25 Sep 2026 12:22:34 +0200 [thread overview]
Message-ID: <2026092555-CVE-2026-97574-b2bb@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
bnxt_en: Don't free the live ring's TPA state on queue restart failure
bnxt_queue_mem_alloc() shallow copies the live RX ring into the clone:
memcpy(clone, rxr, sizeof(*rxr));
the code currently clears pointers that the clone owns (such as
rx_agg_bmap), but rx_tpa and rx_tpa_idx_map are left pointing at memory
of the live ring that was cloned.
If an allocation failure happens later and the err_free_tpa_info label
is taken, the live ring's memory can be freed while still in use.
Fix this by initializing the clone's pointers to NULL to prevent live
ring state from being freed inadvertently.
The Linux kernel CVE team has assigned CVE-2026-97574 to this issue.
Affected and fixed versions
===========================
Issue introduced in 6.13 with commit bd649c5cc958169b8a8a3e77ea926d92d472b02a and fixed in 6.18.53 with commit 8ade95619cbfd1fc57f0f1a9a5ebdca2345a8d27
Issue introduced in 6.13 with commit bd649c5cc958169b8a8a3e77ea926d92d472b02a and fixed in 7.2.7 with commit 0596a7caa6fc283e142716739099c038d8714082
Issue introduced in 6.13 with commit bd649c5cc958169b8a8a3e77ea926d92d472b02a and fixed in 7.3-rc3 with commit 5ce7f36c334d723954855ac769ede2fe0e8f89c8
Issue introduced in 6.12.20 with commit 0997443906b96a051011f220a61e6dce4602ec54
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-97574
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/net/ethernet/broadcom/bnxt/bnxt.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/8ade95619cbfd1fc57f0f1a9a5ebdca2345a8d27
https://git.kernel.org/stable/c/0596a7caa6fc283e142716739099c038d8714082
https://git.kernel.org/stable/c/5ce7f36c334d723954855ac769ede2fe0e8f89c8
reply other threads:[~2026-09-25 10:27 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=2026092555-CVE-2026-97574-b2bb@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.