Answer in brief
CVE-2026-31395 records a Unknown severity vulnerability in bnxt_en: fix OOB access in DBG_BUF_PRODUCER async event handler. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=84fcd9449fd7882ddfb05ba64d75f9be2d29b2e9 <19aa416eed9e4aaf1bbe8da0f7bd9a9be31158c8 || >=84fcd9449fd7882ddfb05ba64d75f9be2d29b2e9 <b7c7a275447c6d4bf4a36a134682e2e4e20efd4b || >=84fcd9449fd7882ddfb05ba64d75f9be2d29b2e9 <64dcbde7f8f870a4f2d9daf24ffb06f9748b5dd3 | 19aa416eed9e4aaf1bbe8da0f7bd9a9be31158c8, b7c7a275447c6d4bf4a36a134682e2e4e20efd4b, 64dcbde7f8f870a4f2d9daf24ffb06f9748b5dd3 |
| Linux/Linuxgeneric | 6.13 | Not reported |
Published upstream
Apr 3, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Nov 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Nov 5, 2026
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).
Quoted source text, attributed separately from HOL analysis.