<?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:10:00 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2026-98989</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2026-98989</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-98989</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-391548</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-391548</link>
      <description>EUVD-2026-391548</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-391548</guid>
    </item>
    <item>
      <title>fkie_cve-2026-98989</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-98989</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;namespace: check a recursive bind mount for mount namespace loops&lt;/p&gt;
&lt;p&gt;do_loopback() refuses to bind mount the file of a mount namespace that
is as old as the caller&amp;#39;s or older because a mount namespace that holds
a mount of its own file, or of an ancestor&amp;#39;s, would cause a cycle. But
it only checks the dentry the bind mount starts from. With MS_REC
everything below it is copied and do_loopback() passes
CL_COPY_MNT_NS_FILE so mount namespace files below the source are
copied.&lt;/p&gt;
&lt;p&gt;That&amp;#39;s fine for a source in the caller&amp;#39;s own mount namespace. Every
mount namespace file in there passed the same check when it was
bind-mounted. It isn&amp;#39;t fine for a source in another mount namespace.
may_copy_tree() accepts a bind mount of any nsfs or pidfs file no matter
what mount namespace it lives in so that /proc/&amp;lt;pid&amp;gt;/ns/&amp;lt;ns&amp;gt; and pidfds
can be bind mounted. If we create a bind-mount stack of mount namespaces
file descriptors the kernel will copy them irrespective of their
ancestoral relationship to the mount namespace in question:&lt;/p&gt;
&lt;p&gt;151 146 0:7 net:[4026531833] /tmp/nrc/y rw - nsfs nsfs rw
  152 151 0:7 mnt:[4026532293] /tmp/nrc/y rw - nsfs nsfs rw&lt;/p&gt;
&lt;p&gt;Mount 152 is a mount of the mount namespace file of mount namespace
4026532293 inside mount namespace 4026532293. That namespace and every
mount in it are leaked... All it takes is a process in an older mount
namespace that stacks the file and repeating it leaks without limit:&lt;/p&gt;
&lt;p&gt;after…&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;namespace: check a recursive bind mount for mount namespace loops&lt;/p&gt;
&lt;p&gt;do_loopback() refuses to bind mount the file of a mount namespace that
is as old as the caller&amp;#39;s or older because a mount namespace that holds
a mount of its own file, or of an ancestor&amp;#39;s, would cause a cycle. But
it only checks the dentry the bind mount starts from. With MS_REC
everything below it is copied and do_loopback() passes
CL_COPY_MNT_NS_FILE so mount namespace files below the source are
copied.&lt;/p&gt;
&lt;p&gt;That&amp;#39;s fine for a source in the caller&amp;#39;s own mount namespace. Every
mount namespace file in there passed the same check when it was
bind-mounted. It isn&amp;#39;t fine for a source in another mount namespace.
may_copy_tree() accepts a bind mount of any nsfs or pidfs file no matter
what mount namespace it lives in so that /proc/&amp;lt;pid&amp;gt;/ns/&amp;lt;ns&amp;gt; and pidfds
can be bind mounted. If we create a bind-mount stack of mount namespaces
file descriptors the kernel will copy them irrespective of their
ancestoral relationship to the mount namespace in question:&lt;/p&gt;
&lt;p&gt;151 146 0:7 net:[4026531833] /tmp/nrc/y rw - nsfs nsfs rw
  152 151 0:7 mnt:[4026532293] /tmp/nrc/y rw - nsfs nsfs rw&lt;/p&gt;
&lt;p&gt;Mount 152 is a mount of the mount namespace file of mount namespace
4026532293 inside mount namespace 4026532293. That namespace and every
mount in it are leaked... All it takes is a process in an older mount
namespace that stacks the file and repeating it leaks without limit:&lt;/p&gt;
&lt;p&gt;after…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-98989</guid>
    </item>
    <item>
      <title>GHSA-88xj-3p4j-2c73</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-88xj-3p4j-2c73</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;namespace: check a recursive bind mount for mount namespace loops&lt;/p&gt;
&lt;p&gt;do_loopback() refuses to bind mount the file of a mount namespace that
is as old as the caller&amp;#39;s or older because a mount namespace that holds
a mount of its own file, or of an ancestor&amp;#39;s, would cause a cycle. But
it only checks the dentry the bind mount starts from. With MS_REC
everything below it is copied and do_loopback() passes
CL_COPY_MNT_NS_FILE so mount namespace files below the source are
copied.&lt;/p&gt;
&lt;p&gt;That&amp;#39;s fine for a source in the caller&amp;#39;s own mount namespace. Every
mount namespace file in there passed the same check when it was
bind-mounted. It isn&amp;#39;t fine for a source in another mount namespace.
may_copy_tree() accepts a bind mount of any nsfs or pidfs file no matter
what mount namespace it lives in so that /proc/&amp;lt;pid&amp;gt;/ns/&amp;lt;ns&amp;gt; and pidfds
can be bind mounted. If we create a bind-mount stack of mount namespaces
file descriptors the kernel will copy them irrespective of their
ancestoral relationship to the mount namespace in question:&lt;/p&gt;
&lt;p&gt;151 146 0:7 net:[4026531833] /tmp/nrc/y rw - nsfs nsfs rw
  152 151 0:7 mnt:[4026532293] /tmp/nrc/y rw - nsfs nsfs rw&lt;/p&gt;
&lt;p&gt;Mount 152 is a mount of the mount namespace file of mount namespace
4026532293 inside mount namespace 4026532293. That namespace and every
mount in it are leaked... All it takes is a process in an older mount
namespace that stacks the file and repeating it leaks without limit:&lt;/p&gt;
&lt;p&gt;after…&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;namespace: check a recursive bind mount for mount namespace loops&lt;/p&gt;
&lt;p&gt;do_loopback() refuses to bind mount the file of a mount namespace that
is as old as the caller&amp;#39;s or older because a mount namespace that holds
a mount of its own file, or of an ancestor&amp;#39;s, would cause a cycle. But
it only checks the dentry the bind mount starts from. With MS_REC
everything below it is copied and do_loopback() passes
CL_COPY_MNT_NS_FILE so mount namespace files below the source are
copied.&lt;/p&gt;
&lt;p&gt;That&amp;#39;s fine for a source in the caller&amp;#39;s own mount namespace. Every
mount namespace file in there passed the same check when it was
bind-mounted. It isn&amp;#39;t fine for a source in another mount namespace.
may_copy_tree() accepts a bind mount of any nsfs or pidfs file no matter
what mount namespace it lives in so that /proc/&amp;lt;pid&amp;gt;/ns/&amp;lt;ns&amp;gt; and pidfds
can be bind mounted. If we create a bind-mount stack of mount namespaces
file descriptors the kernel will copy them irrespective of their
ancestoral relationship to the mount namespace in question:&lt;/p&gt;
&lt;p&gt;151 146 0:7 net:[4026531833] /tmp/nrc/y rw - nsfs nsfs rw
  152 151 0:7 mnt:[4026532293] /tmp/nrc/y rw - nsfs nsfs rw&lt;/p&gt;
&lt;p&gt;Mount 152 is a mount of the mount namespace file of mount namespace
4026532293 inside mount namespace 4026532293. That namespace and every
mount in it are leaked... All it takes is a process in an older mount
namespace that stacks the file and repeating it leaks without limit:&lt;/p&gt;
&lt;p&gt;after…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-88xj-3p4j-2c73</guid>
    </item>
    <item>
      <title>msrc_CVE-2026-98989 — namespace: check a recursive bind mount for mount namespace loops</title>
      <link>https://cve.radiocsirt.org/vuln/msrc_cve-2026-98989</link>
      <description>msrc_CVE-2026-98989</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/msrc_cve-2026-98989</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-98989</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-98989</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: namespace: check a recursive bind mount for mount namespace loops do_loopback() refuses to bind mount the file of a mount namespace that is as old as the caller&amp;#39;s or older because a mount namespace that holds a mount of its own file, or of an ancestor&amp;#39;s, would cause a cycle. But it only checks the dentry the bind mount starts from. With MS_REC everything below it is copied and do_loopback() passes CL_COPY_MNT_NS_FILE so mount namespace files below the source are copied. That&amp;#39;s fine for a source in the caller&amp;#39;s own mount namespace. Every mount namespace file in there passed the same check when it was bind-mounted. It isn&amp;#39;t fine for a source in another mount namespace. may_copy_tree() accepts a bind mount of any nsfs or pidfs file no matter what mount namespace it lives in so that /proc/&amp;lt;pid&amp;gt;/ns/&amp;lt;ns&amp;gt; and pidfds can be bind mounted. If we create a bind-mount stack of mount namespaces file descriptors the kernel will copy them irrespective of their ancestoral relationship to the mount namespace in question:   151 146 0:7 net:[4026531833] /tmp/nrc/y rw - nsfs nsfs rw   152 151 0:7 mnt:[4026532293] /tmp/nrc/y rw - nsfs nsfs rw Mount 152 is a mount of the mount namespace file of mount namespace 4026532293 inside mount namespace 4026532293. That namespace and every mount in it are leaked... All it takes is a process in an older mount namespace that stacks the file and repeating it leaks without limit:   after contro…&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: namespace: check a recursive bind mount for mount namespace loops do_loopback() refuses to bind mount the file of a mount namespace that is as old as the caller&amp;#39;s or older because a mount namespace that holds a mount of its own file, or of an ancestor&amp;#39;s, would cause a cycle. But it only checks the dentry the bind mount starts from. With MS_REC everything below it is copied and do_loopback() passes CL_COPY_MNT_NS_FILE so mount namespace files below the source are copied. That&amp;#39;s fine for a source in the caller&amp;#39;s own mount namespace. Every mount namespace file in there passed the same check when it was bind-mounted. It isn&amp;#39;t fine for a source in another mount namespace. may_copy_tree() accepts a bind mount of any nsfs or pidfs file no matter what mount namespace it lives in so that /proc/&amp;lt;pid&amp;gt;/ns/&amp;lt;ns&amp;gt; and pidfds can be bind mounted. If we create a bind-mount stack of mount namespaces file descriptors the kernel will copy them irrespective of their ancestoral relationship to the mount namespace in question:   151 146 0:7 net:[4026531833] /tmp/nrc/y rw - nsfs nsfs rw   152 151 0:7 mnt:[4026532293] /tmp/nrc/y rw - nsfs nsfs rw Mount 152 is a mount of the mount namespace file of mount namespace 4026532293 inside mount namespace 4026532293. That namespace and every mount in it are leaked... All it takes is a process in an older mount namespace that stacks the file and repeating it leaks without limit:   after contro…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-98989</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>
