<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://vulnerability.circl.lu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-01T15:33:36.827595+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@circl.lu</email>
  </author>
  <link href="https://vulnerability.circl.lu" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/cve-2026-31395</id>
    <title>CVE-2026-31395 — bnxt_en: fix OOB access in DBG_BUF_PRODUCER async event handler</title>
    <updated>2026-10-01T15:33:36.830300+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Linux</p>
<p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>bnxt_en: fix OOB access in DBG_BUF_PRODUCER async event handler</p>
<p>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-&gt;bs_trace[] without bounds validation.</p>
<p>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.</p>
<p>The bnxt_bs_trace_check_wrap() call then dereferences bs_trace-&gt;magic_byte
and writes to bs_trace-&gt;last_offset and bs_trace-&gt;wrapped, leading to
kernel memory corruption or a crash.</p>
<p>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).</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2026-31395"/>
  </entry>
</feed>
