<?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 23:56:52 +0000</lastBuildDate>
    <item>
      <title>CVE-2022-49927 — nfs4: Fix kmemleak when allocate slot failed</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2022-49927</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;nfs4: Fix kmemleak when allocate slot failed&lt;/p&gt;
&lt;p&gt;If one of the slot allocate failed, should cleanup all the other
allocated slots, otherwise, the allocated slots will leak:&lt;/p&gt;
&lt;p&gt;unreferenced object 0xffff8881115aa100 (size 64):
    comm &amp;#34;&amp;#34;mount.nfs&amp;#34;&amp;#34;, pid 679, jiffies 4294744957 (age 115.037s)
    hex dump (first 32 bytes):
      00 cc 19 73 81 88 ff ff 00 a0 5a 11 81 88 ff ff  ...s......Z.....
      00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
    backtrace:
      [&amp;lt;000000007a4c434a&amp;gt;] nfs4_find_or_create_slot+0x8e/0x130
      [&amp;lt;000000005472a39c&amp;gt;] nfs4_realloc_slot_table+0x23f/0x270
      [&amp;lt;00000000cd8ca0eb&amp;gt;] nfs40_init_client+0x4a/0x90
      [&amp;lt;00000000128486db&amp;gt;] nfs4_init_client+0xce/0x270
      [&amp;lt;000000008d2cacad&amp;gt;] nfs4_set_client+0x1a2/0x2b0
      [&amp;lt;000000000e593b52&amp;gt;] nfs4_create_server+0x300/0x5f0
      [&amp;lt;00000000e4425dd2&amp;gt;] nfs4_try_get_tree+0x65/0x110
      [&amp;lt;00000000d3a6176f&amp;gt;] vfs_get_tree+0x41/0xf0
      [&amp;lt;0000000016b5ad4c&amp;gt;] path_mount+0x9b3/0xdd0
      [&amp;lt;00000000494cae71&amp;gt;] __x64_sys_mount+0x190/0x1d0
      [&amp;lt;000000005d56bdec&amp;gt;] do_syscall_64+0x35/0x80
      [&amp;lt;00000000687c9ae4&amp;gt;] entry_SYSCALL_64_after_hwframe+0x46/0xb0&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;nfs4: Fix kmemleak when allocate slot failed&lt;/p&gt;
&lt;p&gt;If one of the slot allocate failed, should cleanup all the other
allocated slots, otherwise, the allocated slots will leak:&lt;/p&gt;
&lt;p&gt;unreferenced object 0xffff8881115aa100 (size 64):
    comm &amp;#34;&amp;#34;mount.nfs&amp;#34;&amp;#34;, pid 679, jiffies 4294744957 (age 115.037s)
    hex dump (first 32 bytes):
      00 cc 19 73 81 88 ff ff 00 a0 5a 11 81 88 ff ff  ...s......Z.....
      00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
    backtrace:
      [&amp;lt;000000007a4c434a&amp;gt;] nfs4_find_or_create_slot+0x8e/0x130
      [&amp;lt;000000005472a39c&amp;gt;] nfs4_realloc_slot_table+0x23f/0x270
      [&amp;lt;00000000cd8ca0eb&amp;gt;] nfs40_init_client+0x4a/0x90
      [&amp;lt;00000000128486db&amp;gt;] nfs4_init_client+0xce/0x270
      [&amp;lt;000000008d2cacad&amp;gt;] nfs4_set_client+0x1a2/0x2b0
      [&amp;lt;000000000e593b52&amp;gt;] nfs4_create_server+0x300/0x5f0
      [&amp;lt;00000000e4425dd2&amp;gt;] nfs4_try_get_tree+0x65/0x110
      [&amp;lt;00000000d3a6176f&amp;gt;] vfs_get_tree+0x41/0xf0
      [&amp;lt;0000000016b5ad4c&amp;gt;] path_mount+0x9b3/0xdd0
      [&amp;lt;00000000494cae71&amp;gt;] __x64_sys_mount+0x190/0x1d0
      [&amp;lt;000000005d56bdec&amp;gt;] do_syscall_64+0x35/0x80
      [&amp;lt;00000000687c9ae4&amp;gt;] entry_SYSCALL_64_after_hwframe+0x46/0xb0&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2022-49927</guid>
    </item>
  </channel>
</rss>
