<?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://cve.radiocsirt.org</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>Wed, 07 Oct 2026 15:15:26 +0000</lastBuildDate>
    <item>
      <title>CVE-2021-47438 — net/mlx5e: Fix memory leak in mlx5_core_destroy_cq() error path</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2021-47438</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/mlx5e: Fix memory leak in mlx5_core_destroy_cq() error path&lt;/p&gt;
&lt;p&gt;Prior to this patch in case mlx5_core_destroy_cq() failed it returns
without completing all destroy operations and that leads to memory leak.
Instead, complete the destroy flow before return error.&lt;/p&gt;
&lt;p&gt;Also move mlx5_debug_cq_remove() to the beginning of mlx5_core_destroy_cq()
to be symmetrical with mlx5_core_create_cq().&lt;/p&gt;
&lt;p&gt;kmemleak complains on:&lt;/p&gt;
&lt;p&gt;unreferenced object 0xc000000038625100 (size 64):
  comm &amp;#34;ethtool&amp;#34;, pid 28301, jiffies 4298062946 (age 785.380s)
  hex dump (first 32 bytes):
    60 01 48 94 00 00 00 c0 b8 05 34 c3 00 00 00 c0  `.H.......4.....
    02 00 00 00 00 00 00 00 00 db 7d c1 00 00 00 c0  ..........}.....
  backtrace:
    [&amp;lt;000000009e8643cb&amp;gt;] add_res_tree+0xd0/0x270 [mlx5_core]
    [&amp;lt;00000000e7cb8e6c&amp;gt;] mlx5_debug_cq_add+0x5c/0xc0 [mlx5_core]
    [&amp;lt;000000002a12918f&amp;gt;] mlx5_core_create_cq+0x1d0/0x2d0 [mlx5_core]
    [&amp;lt;00000000cef0a696&amp;gt;] mlx5e_create_cq+0x210/0x3f0 [mlx5_core]
    [&amp;lt;000000009c642c26&amp;gt;] mlx5e_open_cq+0xb4/0x130 [mlx5_core]
    [&amp;lt;0000000058dfa578&amp;gt;] mlx5e_ptp_open+0x7f4/0xe10 [mlx5_core]
    [&amp;lt;0000000081839561&amp;gt;] mlx5e_open_channels+0x9cc/0x13e0 [mlx5_core]
    [&amp;lt;0000000009cf05d4&amp;gt;] mlx5e_switch_priv_channels+0xa4/0x230
[mlx5_core]
    [&amp;lt;0000000042bbedd8&amp;gt;] mlx5e_safe_switch_params+0x14c/0x300
[mlx5_core]
    [&amp;lt;0000000004bc9db8&amp;gt;] set_pflag_tx_port_ts+0x9c/0x160 [mlx5_core]
    [&amp;lt;00000000a0553443&amp;gt;] mlx5e_set_priv_flags+0xd0…&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/mlx5e: Fix memory leak in mlx5_core_destroy_cq() error path&lt;/p&gt;
&lt;p&gt;Prior to this patch in case mlx5_core_destroy_cq() failed it returns
without completing all destroy operations and that leads to memory leak.
Instead, complete the destroy flow before return error.&lt;/p&gt;
&lt;p&gt;Also move mlx5_debug_cq_remove() to the beginning of mlx5_core_destroy_cq()
to be symmetrical with mlx5_core_create_cq().&lt;/p&gt;
&lt;p&gt;kmemleak complains on:&lt;/p&gt;
&lt;p&gt;unreferenced object 0xc000000038625100 (size 64):
  comm &amp;#34;ethtool&amp;#34;, pid 28301, jiffies 4298062946 (age 785.380s)
  hex dump (first 32 bytes):
    60 01 48 94 00 00 00 c0 b8 05 34 c3 00 00 00 c0  `.H.......4.....
    02 00 00 00 00 00 00 00 00 db 7d c1 00 00 00 c0  ..........}.....
  backtrace:
    [&amp;lt;000000009e8643cb&amp;gt;] add_res_tree+0xd0/0x270 [mlx5_core]
    [&amp;lt;00000000e7cb8e6c&amp;gt;] mlx5_debug_cq_add+0x5c/0xc0 [mlx5_core]
    [&amp;lt;000000002a12918f&amp;gt;] mlx5_core_create_cq+0x1d0/0x2d0 [mlx5_core]
    [&amp;lt;00000000cef0a696&amp;gt;] mlx5e_create_cq+0x210/0x3f0 [mlx5_core]
    [&amp;lt;000000009c642c26&amp;gt;] mlx5e_open_cq+0xb4/0x130 [mlx5_core]
    [&amp;lt;0000000058dfa578&amp;gt;] mlx5e_ptp_open+0x7f4/0xe10 [mlx5_core]
    [&amp;lt;0000000081839561&amp;gt;] mlx5e_open_channels+0x9cc/0x13e0 [mlx5_core]
    [&amp;lt;0000000009cf05d4&amp;gt;] mlx5e_switch_priv_channels+0xa4/0x230
[mlx5_core]
    [&amp;lt;0000000042bbedd8&amp;gt;] mlx5e_safe_switch_params+0x14c/0x300
[mlx5_core]
    [&amp;lt;0000000004bc9db8&amp;gt;] set_pflag_tx_port_ts+0x9c/0x160 [mlx5_core]
    [&amp;lt;00000000a0553443&amp;gt;] mlx5e_set_priv_flags+0xd0…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2021-47438</guid>
    </item>
  </channel>
</rss>
