CVE-2026-31395
bnxt_en: fix OOB access in DBG_BUF_PRODUCER async event handler
Description
In the Linux kernel, the following vulnerability has been resolved: bnxt_en: fix OOB access in DBG_BUF_PRODUCER async event handler The ASYNC_EVENT_CMPL_EVENT_ID_DBG_BUF_PRODUCER handler in bnxt_async_event_process() uses a firmware-supplied 'type' field directly as an index into bp->bs_trace[] without bounds validation. The 'type' field is a 16-bit value extracted from DMA-mapped completion ring memory that the NIC writes directly to host RAM. A malicious or compromised NIC can supply any value from 0 to 65535, causing an out-of-bounds access into kernel heap memory. The bnxt_bs_trace_check_wrap() call then dereferences bs_trace->magic_byte and writes to bs_trace->last_offset and bs_trace->wrapped, leading to kernel memory corruption or a crash. Fix by adding a bounds check and defining BNXT_TRACE_MAX as DBG_LOG_BUFFER_FLUSH_REQ_TYPE_ERR_QPC_TRACE + 1 to cover all currently defined firmware trace types (0x0 through 0xc).
INFO
Published Date :
April 3, 2026, 4:16 p.m.
Last Modified :
July 24, 2026, 10:10 p.m.
Remotely Exploit :
No
Source :
416baaa9-dc9f-4396-8d5f-8c081fb06d67
CVSS Scores
| Score | Version | Severity | Vector | Exploitability Score | Impact Score | Source |
|---|---|---|---|---|---|---|
| CVSS 3.1 | HIGH | [email protected] |
Solution
- Update the Linux kernel to the latest version.
- Apply the specific patch for bnxt_en vulnerability.
- Validate the firmware trace type bounds.
- Ensure proper memory access controls are in place.
References to Advisories, Solutions, and Tools
Here, you will find a curated list of external links that provide in-depth
information, practical solutions, and valuable tools related to
CVE-2026-31395.
CWE - Common Weakness Enumeration
While CVE identifies
specific instances of vulnerabilities, CWE categorizes the common flaws or
weaknesses that can lead to vulnerabilities. CVE-2026-31395 is
associated with the following CWEs:
Common Attack Pattern Enumeration and Classification (CAPEC)
Common Attack Pattern Enumeration and Classification
(CAPEC)
stores attack patterns, which are descriptions of the common attributes and
approaches employed by adversaries to exploit the CVE-2026-31395
weaknesses.
We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).
Results are limited to the first 15 repositories due to potential performance issues.
The following list is the news that have been mention
CVE-2026-31395 vulnerability anywhere in the article.
The following table lists the changes that have been made to the
CVE-2026-31395 vulnerability over time.
Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.
-
CVE Translated by [email protected]
Jul. 24, 2026
Action Type Old Value New Value Added Translation Title: Linux, Description: En el kernel de Linux, la siguiente vulnerabilidad ha sido resuelta: bnxt_en: corrección de acceso fuera de límites en el gestor de eventos asíncronos DBG_BUF_PRODUCER El gestor ASYNC_EVENT_CMPL_EVENT_ID_DBG_BUF_PRODUCER en bnxt_async_event_process() utiliza un campo 'type' proporcionado por el firmware directamente como un índice en bp -> bs_trace[] sin validación de límites. El campo 'type' es un valor de 16 bits extraído de la memoria del anillo de finalización mapeada por DMA que la NIC escribe directamente en la RAM del host. Una NIC maliciosa o comprometida puede proporcionar cualquier valor de 0 a 65535, causando un acceso fuera de límites en la memoria del heap del kernel. La llamada a bnxt_bs_trace_check_wrap() luego desreferencia bs_trace -> magic_byte y escribe en bs_trace -> last_offset y bs_trace -> wrapped, lo que lleva a corrupción de memoria del kernel o a un fallo. Solución mediante la adición de una comprobación de límites y la definición de BNXT_TRACE_MAX como DBG_LOG_BUFFER_FLUSH_REQ_TYPE_ERR_QPC_TRACE + 1 para cubrir todos los tipos de traza de firmware actualmente definidos (de 0x0 a 0xc). -
CVE Modified by 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Jun. 17, 2026
Action Type Old Value New Value Added Affected [{'repo': 'https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git', 'vendor': 'Linux', 'product': 'Linux', 'versions': [{'status': 'affected', 'version': '84fcd9449fd7882ddfb05ba64d75f9be2d29b2e9', 'lessThan': '19aa416eed9e4aaf1bbe8da0f7bd9a9be31158c8', 'versionType': 'git'}, {'status': 'affected', 'version': '84fcd9449fd7882ddfb05ba64d75f9be2d29b2e9', 'lessThan': 'b7c7a275447c6d4bf4a36a134682e2e4e20efd4b', 'versionType': 'git'}, {'status': 'affected', 'version': '84fcd9449fd7882ddfb05ba64d75f9be2d29b2e9', 'lessThan': '64dcbde7f8f870a4f2d9daf24ffb06f9748b5dd3', 'versionType': 'git'}], 'programFiles': ['drivers/net/ethernet/broadcom/bnxt/bnxt.c', 'drivers/net/ethernet/broadcom/bnxt/bnxt.h'], 'defaultStatus': 'unaffected'}, {'repo': 'https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git', 'vendor': 'Linux', 'product': 'Linux', 'versions': [{'status': 'affected', 'version': '6.13'}, {'status': 'unaffected', 'version': '0', 'lessThan': '6.13', 'versionType': 'semver'}, {'status': 'unaffected', 'version': '6.18.20', 'versionType': 'semver', 'lessThanOrEqual': '6.18.*'}, {'status': 'unaffected', 'version': '6.19.10', 'versionType': 'semver', 'lessThanOrEqual': '6.19.*'}, {'status': 'unaffected', 'version': '7.0', 'versionType': 'original_commit_for_fix', 'lessThanOrEqual': '*'}], 'programFiles': ['drivers/net/ethernet/broadcom/bnxt/bnxt.c', 'drivers/net/ethernet/broadcom/bnxt/bnxt.h'], 'defaultStatus': 'affected'}] -
Initial Analysis by [email protected]
May. 20, 2026
Action Type Old Value New Value Added CVSS V3.1 AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H Added CWE CWE-125 Added CPE Configuration OR *cpe:2.3:o:linux:linux_kernel:7.0:rc1:*:*:*:*:*:* *cpe:2.3:o:linux:linux_kernel:7.0:rc2:*:*:*:*:*:* *cpe:2.3:o:linux:linux_kernel:7.0:rc3:*:*:*:*:*:* *cpe:2.3:o:linux:linux_kernel:7.0:rc4:*:*:*:*:*:* *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 6.13 up to (excluding) 6.18.20 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 6.19 up to (excluding) 6.19.10 Added Reference Type kernel.org: https://git.kernel.org/stable/c/19aa416eed9e4aaf1bbe8da0f7bd9a9be31158c8 Types: Patch Added Reference Type kernel.org: https://git.kernel.org/stable/c/64dcbde7f8f870a4f2d9daf24ffb06f9748b5dd3 Types: Patch Added Reference Type kernel.org: https://git.kernel.org/stable/c/b7c7a275447c6d4bf4a36a134682e2e4e20efd4b Types: Patch -
New CVE Received by 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Apr. 03, 2026
Action Type Old Value New Value Added Description In the Linux kernel, the following vulnerability has been resolved: bnxt_en: fix OOB access in DBG_BUF_PRODUCER async event handler The ASYNC_EVENT_CMPL_EVENT_ID_DBG_BUF_PRODUCER handler in bnxt_async_event_process() uses a firmware-supplied 'type' field directly as an index into bp->bs_trace[] without bounds validation. The 'type' field is a 16-bit value extracted from DMA-mapped completion ring memory that the NIC writes directly to host RAM. A malicious or compromised NIC can supply any value from 0 to 65535, causing an out-of-bounds access into kernel heap memory. The bnxt_bs_trace_check_wrap() call then dereferences bs_trace->magic_byte and writes to bs_trace->last_offset and bs_trace->wrapped, leading to kernel memory corruption or a crash. Fix by adding a bounds check and defining BNXT_TRACE_MAX as DBG_LOG_BUFFER_FLUSH_REQ_TYPE_ERR_QPC_TRACE + 1 to cover all currently defined firmware trace types (0x0 through 0xc). Added Reference https://git.kernel.org/stable/c/19aa416eed9e4aaf1bbe8da0f7bd9a9be31158c8 Added Reference https://git.kernel.org/stable/c/64dcbde7f8f870a4f2d9daf24ffb06f9748b5dd3 Added Reference https://git.kernel.org/stable/c/b7c7a275447c6d4bf4a36a134682e2e4e20efd4b