<?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>Tue, 29 Sep 2026 18:24:45 +0000</lastBuildDate>
    <item>
      <title>CVE-2022-50352 — net: hns: fix possible memory leak in hnae_ae_register()</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2022-50352</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: hns: fix possible memory leak in hnae_ae_register()&lt;/p&gt;
&lt;p&gt;Inject fault while probing module, if device_register() fails,
but the refcount of kobject is not decreased to 0, the name
allocated in dev_set_name() is leaked. Fix this by calling
put_device(), so that name can be freed in callback function
kobject_cleanup().&lt;/p&gt;
&lt;p&gt;unreferenced object 0xffff00c01aba2100 (size 128):
  comm &amp;#34;systemd-udevd&amp;#34;, pid 1259, jiffies 4294903284 (age 294.152s)
  hex dump (first 32 bytes):
    68 6e 61 65 30 00 00 00 18 21 ba 1a c0 00 ff ff  hnae0....!......
    00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
  backtrace:
    [&amp;lt;0000000034783f26&amp;gt;] slab_post_alloc_hook+0xa0/0x3e0
    [&amp;lt;00000000748188f2&amp;gt;] __kmem_cache_alloc_node+0x164/0x2b0
    [&amp;lt;00000000ab0743e8&amp;gt;] __kmalloc_node_track_caller+0x6c/0x390
    [&amp;lt;000000006c0ffb13&amp;gt;] kvasprintf+0x8c/0x118
    [&amp;lt;00000000fa27bfe1&amp;gt;] kvasprintf_const+0x60/0xc8
    [&amp;lt;0000000083e10ed7&amp;gt;] kobject_set_name_vargs+0x3c/0xc0
    [&amp;lt;000000000b87affc&amp;gt;] dev_set_name+0x7c/0xa0
    [&amp;lt;000000003fd8fe26&amp;gt;] hnae_ae_register+0xcc/0x190 [hnae]
    [&amp;lt;00000000fe97edc9&amp;gt;] hns_dsaf_ae_init+0x9c/0x108 [hns_dsaf]
    [&amp;lt;00000000c36ff1eb&amp;gt;] hns_dsaf_probe+0x548/0x748 [hns_dsaf]&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: hns: fix possible memory leak in hnae_ae_register()&lt;/p&gt;
&lt;p&gt;Inject fault while probing module, if device_register() fails,
but the refcount of kobject is not decreased to 0, the name
allocated in dev_set_name() is leaked. Fix this by calling
put_device(), so that name can be freed in callback function
kobject_cleanup().&lt;/p&gt;
&lt;p&gt;unreferenced object 0xffff00c01aba2100 (size 128):
  comm &amp;#34;systemd-udevd&amp;#34;, pid 1259, jiffies 4294903284 (age 294.152s)
  hex dump (first 32 bytes):
    68 6e 61 65 30 00 00 00 18 21 ba 1a c0 00 ff ff  hnae0....!......
    00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
  backtrace:
    [&amp;lt;0000000034783f26&amp;gt;] slab_post_alloc_hook+0xa0/0x3e0
    [&amp;lt;00000000748188f2&amp;gt;] __kmem_cache_alloc_node+0x164/0x2b0
    [&amp;lt;00000000ab0743e8&amp;gt;] __kmalloc_node_track_caller+0x6c/0x390
    [&amp;lt;000000006c0ffb13&amp;gt;] kvasprintf+0x8c/0x118
    [&amp;lt;00000000fa27bfe1&amp;gt;] kvasprintf_const+0x60/0xc8
    [&amp;lt;0000000083e10ed7&amp;gt;] kobject_set_name_vargs+0x3c/0xc0
    [&amp;lt;000000000b87affc&amp;gt;] dev_set_name+0x7c/0xa0
    [&amp;lt;000000003fd8fe26&amp;gt;] hnae_ae_register+0xcc/0x190 [hnae]
    [&amp;lt;00000000fe97edc9&amp;gt;] hns_dsaf_ae_init+0x9c/0x108 [hns_dsaf]
    [&amp;lt;00000000c36ff1eb&amp;gt;] hns_dsaf_probe+0x548/0x748 [hns_dsaf]&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2022-50352</guid>
    </item>
  </channel>
</rss>
