<?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 15:15:59 +0000</lastBuildDate>
    <item>
      <title>CVE-2025-40268 — cifs: client: fix memory leak in smb3_fs_context_parse_param</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2025-40268</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: client: fix memory leak in smb3_fs_context_parse_param&lt;/p&gt;
&lt;p&gt;The user calls fsconfig twice, but when the program exits, free() only
frees ctx-&amp;gt;source for the second fsconfig, not the first.
Regarding fc-&amp;gt;source, there is no code in the fs context related to its
memory reclamation.&lt;/p&gt;
&lt;p&gt;To fix this memory leak, release the source memory corresponding to ctx
or fc before each parsing.&lt;/p&gt;
&lt;p&gt;syzbot reported:
BUG: memory leak
unreferenced object 0xffff888128afa360 (size 96):
  backtrace (crc 79c9c7ba):
    kstrdup+0x3c/0x80 mm/util.c:84
    smb3_fs_context_parse_param+0x229b/0x36c0 fs/smb/client/fs_context.c:1444&lt;/p&gt;
&lt;p&gt;BUG: memory leak
unreferenced object 0xffff888112c7d900 (size 96):
  backtrace (crc 79c9c7ba):
    smb3_fs_context_fullpath+0x70/0x1b0 fs/smb/client/fs_context.c:629
    smb3_fs_context_parse_param+0x2266/0x36c0 fs/smb/client/fs_context.c:1438&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: client: fix memory leak in smb3_fs_context_parse_param&lt;/p&gt;
&lt;p&gt;The user calls fsconfig twice, but when the program exits, free() only
frees ctx-&amp;gt;source for the second fsconfig, not the first.
Regarding fc-&amp;gt;source, there is no code in the fs context related to its
memory reclamation.&lt;/p&gt;
&lt;p&gt;To fix this memory leak, release the source memory corresponding to ctx
or fc before each parsing.&lt;/p&gt;
&lt;p&gt;syzbot reported:
BUG: memory leak
unreferenced object 0xffff888128afa360 (size 96):
  backtrace (crc 79c9c7ba):
    kstrdup+0x3c/0x80 mm/util.c:84
    smb3_fs_context_parse_param+0x229b/0x36c0 fs/smb/client/fs_context.c:1444&lt;/p&gt;
&lt;p&gt;BUG: memory leak
unreferenced object 0xffff888112c7d900 (size 96):
  backtrace (crc 79c9c7ba):
    smb3_fs_context_fullpath+0x70/0x1b0 fs/smb/client/fs_context.c:629
    smb3_fs_context_parse_param+0x2266/0x36c0 fs/smb/client/fs_context.c:1438&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2025-40268</guid>
    </item>
  </channel>
</rss>
