<?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>Fri, 02 Oct 2026 14:36:38 +0000</lastBuildDate>
    <item>
      <title>CVE-2022-50702 — vdpa_sim: fix possible memory leak in vdpasim_net_init() and vdpasim_blk_init()</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2022-50702</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;vdpa_sim: fix possible memory leak in vdpasim_net_init() and vdpasim_blk_init()&lt;/p&gt;
&lt;p&gt;Inject fault while probing module, if device_register() fails in
vdpasim_net_init() or vdpasim_blk_init(), 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;(vdpa_sim_net)
unreferenced object 0xffff88807eebc370 (size 16):
  comm &amp;#34;modprobe&amp;#34;, pid 3848, jiffies 4362982860 (age 18.153s)
  hex dump (first 16 bytes):
    76 64 70 61 73 69 6d 5f 6e 65 74 00 6b 6b 6b a5  vdpasim_net.kkk.
  backtrace:
    [&amp;lt;ffffffff8174f19e&amp;gt;] __kmalloc_node_track_caller+0x4e/0x150
    [&amp;lt;ffffffff81731d53&amp;gt;] kstrdup+0x33/0x60
    [&amp;lt;ffffffff83a5d421&amp;gt;] kobject_set_name_vargs+0x41/0x110
    [&amp;lt;ffffffff82d87aab&amp;gt;] dev_set_name+0xab/0xe0
    [&amp;lt;ffffffff82d91a23&amp;gt;] device_add+0xe3/0x1a80
    [&amp;lt;ffffffffa0270013&amp;gt;] 0xffffffffa0270013
    [&amp;lt;ffffffff81001c27&amp;gt;] do_one_initcall+0x87/0x2e0
    [&amp;lt;ffffffff813739cb&amp;gt;] do_init_module+0x1ab/0x640
    [&amp;lt;ffffffff81379d20&amp;gt;] load_module+0x5d00/0x77f0
    [&amp;lt;ffffffff8137bc40&amp;gt;] __do_sys_finit_module+0x110/0x1b0
    [&amp;lt;ffffffff83c4d505&amp;gt;] do_syscall_64+0x35/0x80
    [&amp;lt;ffffffff83e0006a&amp;gt;] entry_SYSCALL_64_after_hwframe+0x46/0xb0&lt;/p&gt;
&lt;p&gt;(vdpa_sim_blk)
unreferenced object 0xffff8881070c1250 (size 16):
  comm &amp;#34;modprobe&amp;#34;, pid 6844, jiffies 4364069319 (age 17.572s)
  hex dump (first 16 bytes):
    76 64 7…&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;vdpa_sim: fix possible memory leak in vdpasim_net_init() and vdpasim_blk_init()&lt;/p&gt;
&lt;p&gt;Inject fault while probing module, if device_register() fails in
vdpasim_net_init() or vdpasim_blk_init(), 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;(vdpa_sim_net)
unreferenced object 0xffff88807eebc370 (size 16):
  comm &amp;#34;modprobe&amp;#34;, pid 3848, jiffies 4362982860 (age 18.153s)
  hex dump (first 16 bytes):
    76 64 70 61 73 69 6d 5f 6e 65 74 00 6b 6b 6b a5  vdpasim_net.kkk.
  backtrace:
    [&amp;lt;ffffffff8174f19e&amp;gt;] __kmalloc_node_track_caller+0x4e/0x150
    [&amp;lt;ffffffff81731d53&amp;gt;] kstrdup+0x33/0x60
    [&amp;lt;ffffffff83a5d421&amp;gt;] kobject_set_name_vargs+0x41/0x110
    [&amp;lt;ffffffff82d87aab&amp;gt;] dev_set_name+0xab/0xe0
    [&amp;lt;ffffffff82d91a23&amp;gt;] device_add+0xe3/0x1a80
    [&amp;lt;ffffffffa0270013&amp;gt;] 0xffffffffa0270013
    [&amp;lt;ffffffff81001c27&amp;gt;] do_one_initcall+0x87/0x2e0
    [&amp;lt;ffffffff813739cb&amp;gt;] do_init_module+0x1ab/0x640
    [&amp;lt;ffffffff81379d20&amp;gt;] load_module+0x5d00/0x77f0
    [&amp;lt;ffffffff8137bc40&amp;gt;] __do_sys_finit_module+0x110/0x1b0
    [&amp;lt;ffffffff83c4d505&amp;gt;] do_syscall_64+0x35/0x80
    [&amp;lt;ffffffff83e0006a&amp;gt;] entry_SYSCALL_64_after_hwframe+0x46/0xb0&lt;/p&gt;
&lt;p&gt;(vdpa_sim_blk)
unreferenced object 0xffff8881070c1250 (size 16):
  comm &amp;#34;modprobe&amp;#34;, pid 6844, jiffies 4364069319 (age 17.572s)
  hex dump (first 16 bytes):
    76 64 7…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2022-50702</guid>
    </item>
  </channel>
</rss>
