<?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://cve.radiocsirt.org</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, 17 Nov 2026 10:33:16 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2026-98984</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2026-98984</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:23: linux-lts, Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:23: linux-lts, Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bell-cve-2026-98984</guid>
    </item>
    <item>
      <title>certfr-2026-avi-1537 — De multiples vulnérabilités ont été découvertes dans le noyau Linux d'Ubuntu. Certaines d'entre elles permettent à un a…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2026-avi-1537</link>
      <description>certfr-2026-avi-1537</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2026-avi-1537</guid>
    </item>
    <item>
      <title>EUVD-2026-396114</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-396114</link>
      <description>EUVD-2026-396114</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-396114</guid>
    </item>
    <item>
      <title>fkie_cve-2026-98984</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-98984</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;dcache: don&amp;#39;t put a mountpoint on a dentry that&amp;#39;s being removed&lt;/p&gt;
&lt;p&gt;rmdir(), unlink() and rename() call dont_mount() on the victim and then
detach_mounts() with the victim&amp;#39;s inode locked. do_lock_mount() takes
the inode lock of the mountpoint and checks cant_mount() so a mount
can&amp;#39;t show up after detach_mounts().&lt;/p&gt;
&lt;p&gt;But attach_recursive_mnt() makes a second mountpoint for the root of the
source mount so that the mounts already located at the destination can
be put on top of it. No inode is locked for that one and d_set_mounted()
only refuses a dentry that is unlinked. Between detach_mounts() and
d_delete() the victim is still hashed:&lt;/p&gt;
&lt;p&gt;rmrace: b passed dont_mount() and detach_mounts(), sleeping
  T2: move_mount(S, /tmp/plcant/x, BENEATH) = 0 errno 0 ()
  T1: rmdir(/tmp/plcant/d/b) = 0 errno 0
      109 107 0:61 /d/b//deleted /tmp/plcant/x rw,relatime - tmpfs tmpfs rw
      108 109 0:63 / /tmp/plcant/x rw,relatime - tmpfs T rw&lt;/p&gt;
&lt;p&gt;A bind mount of the directory that&amp;#39;s being removed is moved beneath an
existing mount while the rmdir() is located between the two calls. The
mount ends up on the removed directory and nothing will ever detach it.&lt;/p&gt;
&lt;p&gt;Check cant_mount() in d_set_mounted() as well. dont_mount() raises the
flag under d_lock before detach_mounts() runs so either the mountpoint
is set first and detach_mounts() finds the mount or the flag is seen and
the mount is refused.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;dcache: don&amp;#39;t put a mountpoint on a dentry that&amp;#39;s being removed&lt;/p&gt;
&lt;p&gt;rmdir(), unlink() and rename() call dont_mount() on the victim and then
detach_mounts() with the victim&amp;#39;s inode locked. do_lock_mount() takes
the inode lock of the mountpoint and checks cant_mount() so a mount
can&amp;#39;t show up after detach_mounts().&lt;/p&gt;
&lt;p&gt;But attach_recursive_mnt() makes a second mountpoint for the root of the
source mount so that the mounts already located at the destination can
be put on top of it. No inode is locked for that one and d_set_mounted()
only refuses a dentry that is unlinked. Between detach_mounts() and
d_delete() the victim is still hashed:&lt;/p&gt;
&lt;p&gt;rmrace: b passed dont_mount() and detach_mounts(), sleeping
  T2: move_mount(S, /tmp/plcant/x, BENEATH) = 0 errno 0 ()
  T1: rmdir(/tmp/plcant/d/b) = 0 errno 0
      109 107 0:61 /d/b//deleted /tmp/plcant/x rw,relatime - tmpfs tmpfs rw
      108 109 0:63 / /tmp/plcant/x rw,relatime - tmpfs T rw&lt;/p&gt;
&lt;p&gt;A bind mount of the directory that&amp;#39;s being removed is moved beneath an
existing mount while the rmdir() is located between the two calls. The
mount ends up on the removed directory and nothing will ever detach it.&lt;/p&gt;
&lt;p&gt;Check cant_mount() in d_set_mounted() as well. dont_mount() raises the
flag under d_lock before detach_mounts() runs so either the mountpoint
is set first and detach_mounts() finds the mount or the flag is seen and
the mount is refused.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-98984</guid>
    </item>
    <item>
      <title>GHSA-j5f8-8hqx-2hcr</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-j5f8-8hqx-2hcr</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;dcache: don&amp;#39;t put a mountpoint on a dentry that&amp;#39;s being removed&lt;/p&gt;
&lt;p&gt;rmdir(), unlink() and rename() call dont_mount() on the victim and then
detach_mounts() with the victim&amp;#39;s inode locked. do_lock_mount() takes
the inode lock of the mountpoint and checks cant_mount() so a mount
can&amp;#39;t show up after detach_mounts().&lt;/p&gt;
&lt;p&gt;But attach_recursive_mnt() makes a second mountpoint for the root of the
source mount so that the mounts already located at the destination can
be put on top of it. No inode is locked for that one and d_set_mounted()
only refuses a dentry that is unlinked. Between detach_mounts() and
d_delete() the victim is still hashed:&lt;/p&gt;
&lt;p&gt;rmrace: b passed dont_mount() and detach_mounts(), sleeping
  T2: move_mount(S, /tmp/plcant/x, BENEATH) = 0 errno 0 ()
  T1: rmdir(/tmp/plcant/d/b) = 0 errno 0
      109 107 0:61 /d/b//deleted /tmp/plcant/x rw,relatime - tmpfs tmpfs rw
      108 109 0:63 / /tmp/plcant/x rw,relatime - tmpfs T rw&lt;/p&gt;
&lt;p&gt;A bind mount of the directory that&amp;#39;s being removed is moved beneath an
existing mount while the rmdir() is located between the two calls. The
mount ends up on the removed directory and nothing will ever detach it.&lt;/p&gt;
&lt;p&gt;Check cant_mount() in d_set_mounted() as well. dont_mount() raises the
flag under d_lock before detach_mounts() runs so either the mountpoint
is set first and detach_mounts() finds the mount or the flag is seen and
the mount is refused.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;dcache: don&amp;#39;t put a mountpoint on a dentry that&amp;#39;s being removed&lt;/p&gt;
&lt;p&gt;rmdir(), unlink() and rename() call dont_mount() on the victim and then
detach_mounts() with the victim&amp;#39;s inode locked. do_lock_mount() takes
the inode lock of the mountpoint and checks cant_mount() so a mount
can&amp;#39;t show up after detach_mounts().&lt;/p&gt;
&lt;p&gt;But attach_recursive_mnt() makes a second mountpoint for the root of the
source mount so that the mounts already located at the destination can
be put on top of it. No inode is locked for that one and d_set_mounted()
only refuses a dentry that is unlinked. Between detach_mounts() and
d_delete() the victim is still hashed:&lt;/p&gt;
&lt;p&gt;rmrace: b passed dont_mount() and detach_mounts(), sleeping
  T2: move_mount(S, /tmp/plcant/x, BENEATH) = 0 errno 0 ()
  T1: rmdir(/tmp/plcant/d/b) = 0 errno 0
      109 107 0:61 /d/b//deleted /tmp/plcant/x rw,relatime - tmpfs tmpfs rw
      108 109 0:63 / /tmp/plcant/x rw,relatime - tmpfs T rw&lt;/p&gt;
&lt;p&gt;A bind mount of the directory that&amp;#39;s being removed is moved beneath an
existing mount while the rmdir() is located between the two calls. The
mount ends up on the removed directory and nothing will ever detach it.&lt;/p&gt;
&lt;p&gt;Check cant_mount() in d_set_mounted() as well. dont_mount() raises the
flag under d_lock before detach_mounts() runs so either the mountpoint
is set first and detach_mounts() finds the mount or the flag is seen and
the mount is refused.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-j5f8-8hqx-2hcr</guid>
    </item>
    <item>
      <title>msrc_CVE-2026-98984 — dcache: don't put a mountpoint on a dentry that's being removed</title>
      <link>https://cve.radiocsirt.org/vuln/msrc_cve-2026-98984</link>
      <description>msrc_CVE-2026-98984</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/msrc_cve-2026-98984</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-98984</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-98984</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, Ubuntu:Pro:16.04:LTS: linux, Ubuntu:Pro:16.04:LTS: linux-aws, Ubuntu:Pro:16.04:LTS: linux-aws-hwe, Ubuntu:Pro:16.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-gcp, Ubuntu:Pro:16.04:LTS: linux-hwe, Ubuntu:16.04:LTS: linux-hwe-edge and 256 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: dcache: don&amp;#39;t put a mountpoint on a dentry that&amp;#39;s being removed rmdir(), unlink() and rename() call dont_mount() on the victim and then detach_mounts() with the victim&amp;#39;s inode locked. do_lock_mount() takes the inode lock of the mountpoint and checks cant_mount() so a mount can&amp;#39;t show up after detach_mounts(). But attach_recursive_mnt() makes a second mountpoint for the root of the source mount so that the mounts already located at the destination can be put on top of it. No inode is locked for that one and d_set_mounted() only refuses a dentry that is unlinked. Between detach_mounts() and d_delete() the victim is still hashed:   rmrace: b passed dont_mount() and detach_mounts(), sleeping   T2: move_mount(S, /tmp/plcant/x, BENEATH) = 0 errno 0 ()   T1: rmdir(/tmp/plcant/d/b) = 0 errno 0       109 107 0:61 /d/b//deleted /tmp/plcant/x rw,relatime - tmpfs tmpfs rw       108 109 0:63 / /tmp/plcant/x rw,relatime - tmpfs T rw A bind mount of the directory that&amp;#39;s being removed is moved beneath an existing mount while the rmdir() is located between the two calls. The mount ends up on the removed directory and nothing will ever detach it. Check cant_mount() in d_set_mounted() as well. dont_mount() raises the flag under d_lock before detach_mounts() runs so either the mountpoint is set first and detach_mounts() finds the mount or the flag is seen and the mount is refused.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, Ubuntu:Pro:16.04:LTS: linux, Ubuntu:Pro:16.04:LTS: linux-aws, Ubuntu:Pro:16.04:LTS: linux-aws-hwe, Ubuntu:Pro:16.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-gcp, Ubuntu:Pro:16.04:LTS: linux-hwe, Ubuntu:16.04:LTS: linux-hwe-edge and 256 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: dcache: don&amp;#39;t put a mountpoint on a dentry that&amp;#39;s being removed rmdir(), unlink() and rename() call dont_mount() on the victim and then detach_mounts() with the victim&amp;#39;s inode locked. do_lock_mount() takes the inode lock of the mountpoint and checks cant_mount() so a mount can&amp;#39;t show up after detach_mounts(). But attach_recursive_mnt() makes a second mountpoint for the root of the source mount so that the mounts already located at the destination can be put on top of it. No inode is locked for that one and d_set_mounted() only refuses a dentry that is unlinked. Between detach_mounts() and d_delete() the victim is still hashed:   rmrace: b passed dont_mount() and detach_mounts(), sleeping   T2: move_mount(S, /tmp/plcant/x, BENEATH) = 0 errno 0 ()   T1: rmdir(/tmp/plcant/d/b) = 0 errno 0       109 107 0:61 /d/b//deleted /tmp/plcant/x rw,relatime - tmpfs tmpfs rw       108 109 0:63 / /tmp/plcant/x rw,relatime - tmpfs T rw A bind mount of the directory that&amp;#39;s being removed is moved beneath an existing mount while the rmdir() is located between the two calls. The mount ends up on the removed directory and nothing will ever detach it. Check cant_mount() in d_set_mounted() as well. dont_mount() raises the flag under d_lock before detach_mounts() runs so either the mountpoint is set first and detach_mounts() finds the mount or the flag is seen and the mount is refused.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-98984</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-4152 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-4152</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen, möglicherweise einen Denial-of-Service-Angriff auszulösen, Daten zu manipulieren oder offenzulegen oder Sicherheitsmaßnahmen zu umgehen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen, möglicherweise einen Denial-of-Service-Angriff auszulösen, Daten zu manipulieren oder offenzulegen oder Sicherheitsmaßnahmen zu umgehen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2026-4152</guid>
    </item>
  </channel>
</rss>
