Bug 2422703 (CVE-2025-68197)

Summary:	CVE-2025-68197 kernel: bnxt_en: Fix null pointer dereference in bnxt_bs_trace_check_wrap()
Product:	[Other] Security Response	Reporter:	OSIDB Bzimport <bzimport>
Component:	vulnerability	Assignee:	Product Security DevOps Team <prodsec-dev>
Status:	NEW ---	QA Contact:
Severity:	medium	Docs Contact:
Priority:	medium
Version:	unspecified	CC:	rhel-process-autobot, watson-tool-maintainers
Target Milestone:	---	Keywords:	Security
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	---
Doc Text:	A flaw was identified in the Broadcom NetXtreme-E (bnxt_en) networking driver in the Linux kernel involving improper handling of uninitialized firmware trace event data. Certain firmware versions may report an ASYNC_EVENT_CMPL_EVENT_ID_DBG_BUF_PRODUCER event type without having initialized the corresponding trace buffer pointer (magic_byte). When the driver attempts to process this event in the bnxt_bs_trace_type_wrap() function, it may dereference a NULL or invalid pointer, leading to a kernel crash (NULL pointer dereference).	Story Points:	---
Clone Of:		Environment:
Last Closed:		Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description OSIDB Bzimport 2025-12-16 14:04:59 UTC

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.

Comment 1 Alexander B 2025-12-17 01:50:06 UTC

Upstream advisory:
https://lore.kernel.org/linux-cve-announce/2025121637-CVE-2025-68197-5624@gregkh/T