<?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 23:47:43 +0000</lastBuildDate>
    <item>
      <title>CVE-2025-68219 — cifs: fix memory leak in smb3_fs_context_parse_param error path</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2025-68219</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;cifs: fix memory leak in smb3_fs_context_parse_param error path&lt;/p&gt;
&lt;p&gt;Add proper cleanup of ctx-&amp;gt;source and fc-&amp;gt;source to the
cifs_parse_mount_err error handler. This ensures that memory allocated
for the source strings is correctly freed on all error paths, matching
the cleanup already performed in the success path by
smb3_cleanup_fs_context_contents().
Pointers are also set to NULL after freeing to prevent potential
double-free issues.&lt;/p&gt;
&lt;p&gt;This change fixes a memory leak originally detected by syzbot. The
leak occurred when processing Opt_source mount options if an error
happened after ctx-&amp;gt;source and fc-&amp;gt;source were successfully
allocated but before the function completed.&lt;/p&gt;
&lt;p&gt;The specific leak sequence was:
1. ctx-&amp;gt;source = smb3_fs_context_fullpath(ctx, &amp;#39;/&amp;#39;) allocates memory
2. fc-&amp;gt;source = kstrdup(ctx-&amp;gt;source, GFP_KERNEL) allocates more memory
3. A subsequent error jumps to cifs_parse_mount_err
4. The old error handler freed passwords but not the source strings,
causing the memory to leak.&lt;/p&gt;
&lt;p&gt;This issue was not addressed by commit e8c73eb7db0a (&amp;#34;cifs: client:
fix memory leak in smb3_fs_context_parse_param&amp;#34;), which only fixed
leaks from repeated fsconfig() calls but not this error path.&lt;/p&gt;
&lt;p&gt;Patch updated with minor change suggested by kernel test robot&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;cifs: fix memory leak in smb3_fs_context_parse_param error path&lt;/p&gt;
&lt;p&gt;Add proper cleanup of ctx-&amp;gt;source and fc-&amp;gt;source to the
cifs_parse_mount_err error handler. This ensures that memory allocated
for the source strings is correctly freed on all error paths, matching
the cleanup already performed in the success path by
smb3_cleanup_fs_context_contents().
Pointers are also set to NULL after freeing to prevent potential
double-free issues.&lt;/p&gt;
&lt;p&gt;This change fixes a memory leak originally detected by syzbot. The
leak occurred when processing Opt_source mount options if an error
happened after ctx-&amp;gt;source and fc-&amp;gt;source were successfully
allocated but before the function completed.&lt;/p&gt;
&lt;p&gt;The specific leak sequence was:
1. ctx-&amp;gt;source = smb3_fs_context_fullpath(ctx, &amp;#39;/&amp;#39;) allocates memory
2. fc-&amp;gt;source = kstrdup(ctx-&amp;gt;source, GFP_KERNEL) allocates more memory
3. A subsequent error jumps to cifs_parse_mount_err
4. The old error handler freed passwords but not the source strings,
causing the memory to leak.&lt;/p&gt;
&lt;p&gt;This issue was not addressed by commit e8c73eb7db0a (&amp;#34;cifs: client:
fix memory leak in smb3_fs_context_parse_param&amp;#34;), which only fixed
leaks from repeated fsconfig() calls but not this error path.&lt;/p&gt;
&lt;p&gt;Patch updated with minor change suggested by kernel test robot&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2025-68219</guid>
    </item>
  </channel>
</rss>
