<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://vulnerability.circl.lu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-09-30T06:28:49.036104+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@circl.lu</email>
  </author>
  <link href="https://vulnerability.circl.lu" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/cve-2025-68219</id>
    <title>CVE-2025-68219 — cifs: fix memory leak in smb3_fs_context_parse_param error path</title>
    <updated>2026-09-30T06:28:49.039103+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Linux</p>
<p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>cifs: fix memory leak in smb3_fs_context_parse_param error path</p>
<p>Add proper cleanup of ctx-&gt;source and fc-&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.</p>
<p>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-&gt;source and fc-&gt;source were successfully
allocated but before the function completed.</p>
<p>The specific leak sequence was:
1. ctx-&gt;source = smb3_fs_context_fullpath(ctx, '/') allocates memory
2. fc-&gt;source = kstrdup(ctx-&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.</p>
<p>This issue was not addressed by commit e8c73eb7db0a ("cifs: client:
fix memory leak in smb3_fs_context_parse_param"), which only fixed
leaks from repeated fsconfig() calls but not this error path.</p>
<p>Patch updated with minor change suggested by kernel test robot</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2025-68219"/>
  </entry>
</feed>
