https://vulnerability.circl.lu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Wed, 30 Sep 2026 15:22:32 +0000 https://vulnerability.circl.lu/vuln/cve-2025-40362 <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>ceph: fix multifs mds auth caps issue</p> <p>The mds auth caps check should also validate the fsname along with the associated caps. Not doing so would result in applying the mds auth caps of one fs on to the other fs in a multifs ceph cluster. The bug causes multiple issues w.r.t user authentication, following is one such example.</p> <p>Steps to Reproduce (on vstart cluster): 1. Create two file systems in a cluster, say &#39;fsname1&#39; and &#39;fsname2&#39; 2. Authorize read only permission to the user &#39;client.usr&#39; on fs &#39;fsname1&#39; $ceph fs authorize fsname1 client.usr / r 3. Authorize read and write permission to the same user &#39;client.usr&#39; on fs &#39;fsname2&#39; $ceph fs authorize fsname2 client.usr / rw 4. Update the keyring $ceph auth get client.usr &gt;&gt; ./keyring</p> <p>With above permssions for the user &#39;client.usr&#39;, following is the expectation. a. The &#39;client.usr&#39; should be able to only read the contents and not allowed to create or delete files on file system &#39;fsname1&#39;. b. The &#39;client.usr&#39; should be able to read/write on file system &#39;fsname2&#39;.</p> <p>But, with this bug, the &#39;client.usr&#39; is allowed to read/write on file system &#39;fsname1&#39;. See below.</p> <p>5. Mount the file system &#39;fsname1&#39; with the user &#39;client.usr&#39; $sudo bin/mount.ceph usr@.fsname1=/ /kmnt_fsname1_usr/ 6. Try creating a file on file system &#39;fsname1&#39; with user &#39;client.usr&#39;. This should fail but passes with this bug. $touch /kmnt_fsname1_usr/file1 7. M…</p> <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>ceph: fix multifs mds auth caps issue</p> <p>The mds auth caps check should also validate the fsname along with the associated caps. Not doing so would result in applying the mds auth caps of one fs on to the other fs in a multifs ceph cluster. The bug causes multiple issues w.r.t user authentication, following is one such example.</p> <p>Steps to Reproduce (on vstart cluster): 1. Create two file systems in a cluster, say &#39;fsname1&#39; and &#39;fsname2&#39; 2. Authorize read only permission to the user &#39;client.usr&#39; on fs &#39;fsname1&#39; $ceph fs authorize fsname1 client.usr / r 3. Authorize read and write permission to the same user &#39;client.usr&#39; on fs &#39;fsname2&#39; $ceph fs authorize fsname2 client.usr / rw 4. Update the keyring $ceph auth get client.usr &gt;&gt; ./keyring</p> <p>With above permssions for the user &#39;client.usr&#39;, following is the expectation. a. The &#39;client.usr&#39; should be able to only read the contents and not allowed to create or delete files on file system &#39;fsname1&#39;. b. The &#39;client.usr&#39; should be able to read/write on file system &#39;fsname2&#39;.</p> <p>But, with this bug, the &#39;client.usr&#39; is allowed to read/write on file system &#39;fsname1&#39;. See below.</p> <p>5. Mount the file system &#39;fsname1&#39; with the user &#39;client.usr&#39; $sudo bin/mount.ceph usr@.fsname1=/ /kmnt_fsname1_usr/ 6. Try creating a file on file system &#39;fsname1&#39; with user &#39;client.usr&#39;. This should fail but passes with this bug. $touch /kmnt_fsname1_usr/file1 7. M…</p> https://vulnerability.circl.lu/vuln/cve-2025-40362