<?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>Sat, 03 Oct 2026 22:41:27 +0000</lastBuildDate>
    <item>
      <title>CVE-2025-21737 — ceph: fix memory leak in ceph_mds_auth_match()</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2025-21737</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;ceph: fix memory leak in ceph_mds_auth_match()&lt;/p&gt;
&lt;p&gt;We now free the temporary target path substring allocation on every
possible branch, instead of omitting the default branch.  In some
cases, a memory leak occured, which could rapidly crash the system
(depending on how many file accesses were attempted).&lt;/p&gt;
&lt;p&gt;This was detected in production because it caused a continuous memory
growth, eventually triggering kernel OOM and completely hard-locking
the kernel.&lt;/p&gt;
&lt;p&gt;Relevant kmemleak stacktrace:&lt;/p&gt;
&lt;p&gt;unreferenced object 0xffff888131e69900 (size 128):
      comm &amp;#34;git&amp;#34;, pid 66104, jiffies 4295435999
      hex dump (first 32 bytes):
        76 6f 6c 75 6d 65 73 2f 63 6f 6e 74 61 69 6e 65  volumes/containe
        72 73 2f 67 69 74 65 61 2f 67 69 74 65 61 2f 67  rs/gitea/gitea/g
      backtrace (crc 2f3bb450):
        [&amp;lt;ffffffffaa68fb49&amp;gt;] __kmalloc_noprof+0x359/0x510
        [&amp;lt;ffffffffc32bf1df&amp;gt;] ceph_mds_check_access+0x5bf/0x14e0 [ceph]
        [&amp;lt;ffffffffc3235722&amp;gt;] ceph_open+0x312/0xd80 [ceph]
        [&amp;lt;ffffffffaa7dd786&amp;gt;] do_dentry_open+0x456/0x1120
        [&amp;lt;ffffffffaa7e3729&amp;gt;] vfs_open+0x79/0x360
        [&amp;lt;ffffffffaa832875&amp;gt;] path_openat+0x1de5/0x4390
        [&amp;lt;ffffffffaa834fcc&amp;gt;] do_filp_open+0x19c/0x3c0
        [&amp;lt;ffffffffaa7e44a1&amp;gt;] do_sys_openat2+0x141/0x180
        [&amp;lt;ffffffffaa7e4945&amp;gt;] __x64_sys_open+0xe5/0x1a0
        [&amp;lt;ffffffffac2cc2f7&amp;gt;] do_syscall_64+0xb7/0x210
        [&amp;lt;ffffffffac400130&amp;gt;] entry_SYSCALL_64_after_hwframe+…&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;ceph: fix memory leak in ceph_mds_auth_match()&lt;/p&gt;
&lt;p&gt;We now free the temporary target path substring allocation on every
possible branch, instead of omitting the default branch.  In some
cases, a memory leak occured, which could rapidly crash the system
(depending on how many file accesses were attempted).&lt;/p&gt;
&lt;p&gt;This was detected in production because it caused a continuous memory
growth, eventually triggering kernel OOM and completely hard-locking
the kernel.&lt;/p&gt;
&lt;p&gt;Relevant kmemleak stacktrace:&lt;/p&gt;
&lt;p&gt;unreferenced object 0xffff888131e69900 (size 128):
      comm &amp;#34;git&amp;#34;, pid 66104, jiffies 4295435999
      hex dump (first 32 bytes):
        76 6f 6c 75 6d 65 73 2f 63 6f 6e 74 61 69 6e 65  volumes/containe
        72 73 2f 67 69 74 65 61 2f 67 69 74 65 61 2f 67  rs/gitea/gitea/g
      backtrace (crc 2f3bb450):
        [&amp;lt;ffffffffaa68fb49&amp;gt;] __kmalloc_noprof+0x359/0x510
        [&amp;lt;ffffffffc32bf1df&amp;gt;] ceph_mds_check_access+0x5bf/0x14e0 [ceph]
        [&amp;lt;ffffffffc3235722&amp;gt;] ceph_open+0x312/0xd80 [ceph]
        [&amp;lt;ffffffffaa7dd786&amp;gt;] do_dentry_open+0x456/0x1120
        [&amp;lt;ffffffffaa7e3729&amp;gt;] vfs_open+0x79/0x360
        [&amp;lt;ffffffffaa832875&amp;gt;] path_openat+0x1de5/0x4390
        [&amp;lt;ffffffffaa834fcc&amp;gt;] do_filp_open+0x19c/0x3c0
        [&amp;lt;ffffffffaa7e44a1&amp;gt;] do_sys_openat2+0x141/0x180
        [&amp;lt;ffffffffaa7e4945&amp;gt;] __x64_sys_open+0xe5/0x1a0
        [&amp;lt;ffffffffac2cc2f7&amp;gt;] do_syscall_64+0xb7/0x210
        [&amp;lt;ffffffffac400130&amp;gt;] entry_SYSCALL_64_after_hwframe+…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2025-21737</guid>
    </item>
  </channel>
</rss>
