<?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://db.gcve.eu</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, 12 Nov 2026 07:21:49 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-98486 — net: ena: fix MMIO read buffer leak on probe failure</title>
      <link>https://db.gcve.eu/vuln/cve-2026-98486</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;net: ena: fix MMIO read buffer leak on probe failure&lt;/p&gt;
&lt;p&gt;ena_device_init() initializes the MMIO read mechanism with
ena_com_mmio_reg_read_request_init(), which allocates a coherent DMA
buffer for MMIO read responses.&lt;/p&gt;
&lt;p&gt;The normal removal path releases this buffer through
ena_com_mmio_reg_read_request_destroy(). However, if ena_probe() fails
after ena_device_init() succeeds, the error path destroys the admin
resources and eventually frees ena_dev without destroying the MMIO read
request, leaving the coherent DMA buffer allocated.&lt;/p&gt;
&lt;p&gt;Call ena_com_mmio_reg_read_request_destroy() in the probe error path
before releasing the remaining device resources.&lt;/p&gt;
&lt;p&gt;This issue was found by manual code inspection.&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;net: ena: fix MMIO read buffer leak on probe failure&lt;/p&gt;
&lt;p&gt;ena_device_init() initializes the MMIO read mechanism with
ena_com_mmio_reg_read_request_init(), which allocates a coherent DMA
buffer for MMIO read responses.&lt;/p&gt;
&lt;p&gt;The normal removal path releases this buffer through
ena_com_mmio_reg_read_request_destroy(). However, if ena_probe() fails
after ena_device_init() succeeds, the error path destroys the admin
resources and eventually frees ena_dev without destroying the MMIO read
request, leaving the coherent DMA buffer allocated.&lt;/p&gt;
&lt;p&gt;Call ena_com_mmio_reg_read_request_destroy() in the probe error path
before releasing the remaining device resources.&lt;/p&gt;
&lt;p&gt;This issue was found by manual code inspection.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/cve-2026-98486</guid>
    </item>
  </channel>
</rss>
