[<prev] [next>] [day] [month] [year] [list]
Message-ID: <2025121637-CVE-2025-68197-5624@gregkh>
Date: Tue, 16 Dec 2025 14:43:58 +0100
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...nel.org>
Subject: CVE-2025-68197: bnxt_en: Fix null pointer dereference in bnxt_bs_trace_check_wrap()
From: Greg Kroah-Hartman <gregkh@...nel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
bnxt_en: Fix null pointer dereference in bnxt_bs_trace_check_wrap()
With older FW, we may get the ASYNC_EVENT_CMPL_EVENT_ID_DBG_BUF_PRODUCER
for FW trace data type that has not been initialized. This will result
in a crash in bnxt_bs_trace_type_wrap(). Add a guard to check for a
valid magic_byte pointer before proceeding.
The Linux kernel CVE team has assigned CVE-2025-68197 to this issue.
Affected and fixed versions
===========================
Issue introduced in 6.13 with commit 84fcd9449fd7882ddfb05ba64d75f9be2d29b2e9 and fixed in 6.17.8 with commit 689ae5ba31293eebb7f21c0ef8939468ac72b5ce
Issue introduced in 6.13 with commit 84fcd9449fd7882ddfb05ba64d75f9be2d29b2e9 and fixed in 6.18 with commit ff02be05f78399c766be68ab0b2285ff90b2aaa8
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-2025-68197
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.h
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/689ae5ba31293eebb7f21c0ef8939468ac72b5ce
https://git.kernel.org/stable/c/ff02be05f78399c766be68ab0b2285ff90b2aaa8
Powered by blists - more mailing lists