https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sun, 04 Oct 2026 16:30:13 +0000 https://cve.radiocsirt.org/vuln/bdu:2026-03005 bdu:2026-03005 https://cve.radiocsirt.org/vuln/bdu:2026-03005 https://cve.radiocsirt.org/vuln/bell-cve-2025-40362 <p><strong>Affected:</strong> Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts</p> <p><strong>Affected:</strong> Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts</p> https://cve.radiocsirt.org/vuln/bell-cve-2025-40362 https://cve.radiocsirt.org/vuln/certfr-2026-avi-0128 certfr-2026-avi-0128 https://cve.radiocsirt.org/vuln/certfr-2026-avi-0128 https://cve.radiocsirt.org/vuln/euvd-2026-347444 EUVD-2026-347444 https://cve.radiocsirt.org/vuln/euvd-2026-347444 https://cve.radiocsirt.org/vuln/fkie_cve-2025-40362 <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>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://cve.radiocsirt.org/vuln/fkie_cve-2025-40362 https://cve.radiocsirt.org/vuln/ghsa-p5mp-qv23-7r77 <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>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://cve.radiocsirt.org/vuln/ghsa-p5mp-qv23-7r77 https://cve.radiocsirt.org/vuln/msrc_cve-2025-40362 msrc_CVE-2025-40362 https://cve.radiocsirt.org/vuln/msrc_cve-2025-40362 https://cve.radiocsirt.org/vuln/opensuse-su-2026:20145-1 <p>Security update for the Linux Kernel</p> <p>Security update for the Linux Kernel</p> https://cve.radiocsirt.org/vuln/opensuse-su-2026:20145-1 https://cve.radiocsirt.org/vuln/suse-su-2026:20207-1 <p>Security update for the Linux Kernel</p> <p>Security update for the Linux Kernel</p> https://cve.radiocsirt.org/vuln/suse-su-2026:20207-1 https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-40362 <p><strong>Affected:</strong> Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3, Ubuntu:18.04:LTS: linux-gke-4.15, Ubuntu:18.04:LTS: linux-gke-5.4 and 104 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: ceph: fix multifs mds auth caps issue 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. 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 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;. But, with this bug, the &#39;client.usr&#39; is allowed to read/write on file system &#39;fsname1&#39;. See below. 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. Mount t…</p> <p><strong>Affected:</strong> Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3, Ubuntu:18.04:LTS: linux-gke-4.15, Ubuntu:18.04:LTS: linux-gke-5.4 and 104 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: ceph: fix multifs mds auth caps issue 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. 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 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;. But, with this bug, the &#39;client.usr&#39; is allowed to read/write on file system &#39;fsname1&#39;. See below. 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. Mount t…</p> https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-40362 https://cve.radiocsirt.org/vuln/wid-sec-w-2025-2868 <p>Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um nicht näher spezifizierte Angriffe durchzuführen, die möglicherweise zu einer Denial-of-Service- Bedingung führen oder eine Speicherbeschädigung verursachen können.</p> <p>Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um nicht näher spezifizierte Angriffe durchzuführen, die möglicherweise zu einer Denial-of-Service- Bedingung führen oder eine Speicherbeschädigung verursachen können.</p> https://cve.radiocsirt.org/vuln/wid-sec-w-2025-2868