<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://vulnerability.circl.lu</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Thu, 01 Oct 2026 08:38:04 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-31395 — bnxt_en: fix OOB access in DBG_BUF_PRODUCER async event handler</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-31395</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;bnxt_en: fix OOB access in DBG_BUF_PRODUCER async event handler&lt;/p&gt;
&lt;p&gt;The ASYNC_EVENT_CMPL_EVENT_ID_DBG_BUF_PRODUCER handler in
bnxt_async_event_process() uses a firmware-supplied &amp;#39;type&amp;#39; field
directly as an index into bp-&amp;gt;bs_trace[] without bounds validation.&lt;/p&gt;
&lt;p&gt;The &amp;#39;type&amp;#39; 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.&lt;/p&gt;
&lt;p&gt;The bnxt_bs_trace_check_wrap() call then dereferences bs_trace-&amp;gt;magic_byte
and writes to bs_trace-&amp;gt;last_offset and bs_trace-&amp;gt;wrapped, leading to
kernel memory corruption or a crash.&lt;/p&gt;
&lt;p&gt;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).&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;bnxt_en: fix OOB access in DBG_BUF_PRODUCER async event handler&lt;/p&gt;
&lt;p&gt;The ASYNC_EVENT_CMPL_EVENT_ID_DBG_BUF_PRODUCER handler in
bnxt_async_event_process() uses a firmware-supplied &amp;#39;type&amp;#39; field
directly as an index into bp-&amp;gt;bs_trace[] without bounds validation.&lt;/p&gt;
&lt;p&gt;The &amp;#39;type&amp;#39; 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.&lt;/p&gt;
&lt;p&gt;The bnxt_bs_trace_check_wrap() call then dereferences bs_trace-&amp;gt;magic_byte
and writes to bs_trace-&amp;gt;last_offset and bs_trace-&amp;gt;wrapped, leading to
kernel memory corruption or a crash.&lt;/p&gt;
&lt;p&gt;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).&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-31395</guid>
    </item>
  </channel>
</rss>
