<?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:08 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2026-98993</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2026-98993</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-98993</guid>
    </item>
    <item>
      <title>certfr-2026-avi-1473 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de Debian. Elles permettent à un attaquant de provo…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2026-avi-1473</link>
      <description>certfr-2026-avi-1473</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2026-avi-1473</guid>
    </item>
    <item>
      <title>EUVD-2026-396118</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-396118</link>
      <description>EUVD-2026-396118</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-396118</guid>
    </item>
    <item>
      <title>fkie_cve-2026-98993</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-98993</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;namespace: don&amp;#39;t inherit MNT_UMOUNT in clone_mnt()&lt;/p&gt;
&lt;p&gt;MNT_UMOUNT gets raised on a mount that umount_tree() or umount_one() has
taken out of its namespace. It&amp;#39;s never cleared. __detach_mounts()
unhooks a mount that carries it instead of unmounting it.&lt;/p&gt;
&lt;p&gt;disconnect_mount() lets an unmounted child stay attached only if its
parent carries it. propagate_umount() takes it as the sign that a mount
is going to be unmounted when it decides what else can be unmounted,
where a chain of locked mounts ends and where a for reparenting an
overmount.&lt;/p&gt;
&lt;p&gt;clone_mnt() copies the flags of the source and only masks
MNT_INTERNAL_FLAGS which doesn&amp;#39;t include MNT_UMOUNT. A mount that was
lazily unmounted but is kept alive by a file descriptor can still be
copied when its root is an nsfs or pidfs file because may_copy_tree()
accepts those before checking whether the source is mounted at all:&lt;/p&gt;
&lt;p&gt;mount --bind /proc/self/ns/net /tmp/x
  exec 3&amp;lt; /tmp/x
  umount -l /tmp/x
  mount --bind /proc/self/fd/3 /tmp/y&lt;/p&gt;
&lt;p&gt;The mount on /tmp/y is attached to the caller&amp;#39;s namespace with
MNT_UMOUNT already set and every copy of it inherits the flag again.&lt;/p&gt;
&lt;p&gt;That causes a number of bugs:&lt;/p&gt;
&lt;p&gt;- Unlink its mountpoint from a mount namespace where it isn&amp;#39;t one.
  __detach_mounts() takes it for a mount that was unmounted earlier,
  unhooks it from its parent and drops the reference the namespace
  holds on it. It stays in the namespace with one reference too few
  and…&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: don&amp;#39;t inherit MNT_UMOUNT in clone_mnt()&lt;/p&gt;
&lt;p&gt;MNT_UMOUNT gets raised on a mount that umount_tree() or umount_one() has
taken out of its namespace. It&amp;#39;s never cleared. __detach_mounts()
unhooks a mount that carries it instead of unmounting it.&lt;/p&gt;
&lt;p&gt;disconnect_mount() lets an unmounted child stay attached only if its
parent carries it. propagate_umount() takes it as the sign that a mount
is going to be unmounted when it decides what else can be unmounted,
where a chain of locked mounts ends and where a for reparenting an
overmount.&lt;/p&gt;
&lt;p&gt;clone_mnt() copies the flags of the source and only masks
MNT_INTERNAL_FLAGS which doesn&amp;#39;t include MNT_UMOUNT. A mount that was
lazily unmounted but is kept alive by a file descriptor can still be
copied when its root is an nsfs or pidfs file because may_copy_tree()
accepts those before checking whether the source is mounted at all:&lt;/p&gt;
&lt;p&gt;mount --bind /proc/self/ns/net /tmp/x
  exec 3&amp;lt; /tmp/x
  umount -l /tmp/x
  mount --bind /proc/self/fd/3 /tmp/y&lt;/p&gt;
&lt;p&gt;The mount on /tmp/y is attached to the caller&amp;#39;s namespace with
MNT_UMOUNT already set and every copy of it inherits the flag again.&lt;/p&gt;
&lt;p&gt;That causes a number of bugs:&lt;/p&gt;
&lt;p&gt;- Unlink its mountpoint from a mount namespace where it isn&amp;#39;t one.
  __detach_mounts() takes it for a mount that was unmounted earlier,
  unhooks it from its parent and drops the reference the namespace
  holds on it. It stays in the namespace with one reference too few
  and…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-98993</guid>
    </item>
    <item>
      <title>GHSA-53w5-4v27-r5f4</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-53w5-4v27-r5f4</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;namespace: don&amp;#39;t inherit MNT_UMOUNT in clone_mnt()&lt;/p&gt;
&lt;p&gt;MNT_UMOUNT gets raised on a mount that umount_tree() or umount_one() has
taken out of its namespace. It&amp;#39;s never cleared. __detach_mounts()
unhooks a mount that carries it instead of unmounting it.&lt;/p&gt;
&lt;p&gt;disconnect_mount() lets an unmounted child stay attached only if its
parent carries it. propagate_umount() takes it as the sign that a mount
is going to be unmounted when it decides what else can be unmounted,
where a chain of locked mounts ends and where a for reparenting an
overmount.&lt;/p&gt;
&lt;p&gt;clone_mnt() copies the flags of the source and only masks
MNT_INTERNAL_FLAGS which doesn&amp;#39;t include MNT_UMOUNT. A mount that was
lazily unmounted but is kept alive by a file descriptor can still be
copied when its root is an nsfs or pidfs file because may_copy_tree()
accepts those before checking whether the source is mounted at all:&lt;/p&gt;
&lt;p&gt;mount --bind /proc/self/ns/net /tmp/x
  exec 3&amp;lt; /tmp/x
  umount -l /tmp/x
  mount --bind /proc/self/fd/3 /tmp/y&lt;/p&gt;
&lt;p&gt;The mount on /tmp/y is attached to the caller&amp;#39;s namespace with
MNT_UMOUNT already set and every copy of it inherits the flag again.&lt;/p&gt;
&lt;p&gt;That causes a number of bugs:&lt;/p&gt;
&lt;p&gt;- Unlink its mountpoint from a mount namespace where it isn&amp;#39;t one.
  __detach_mounts() takes it for a mount that was unmounted earlier,
  unhooks it from its parent and drops the reference the namespace
  holds on it. It stays in the namespace with one reference too few
  and…&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: don&amp;#39;t inherit MNT_UMOUNT in clone_mnt()&lt;/p&gt;
&lt;p&gt;MNT_UMOUNT gets raised on a mount that umount_tree() or umount_one() has
taken out of its namespace. It&amp;#39;s never cleared. __detach_mounts()
unhooks a mount that carries it instead of unmounting it.&lt;/p&gt;
&lt;p&gt;disconnect_mount() lets an unmounted child stay attached only if its
parent carries it. propagate_umount() takes it as the sign that a mount
is going to be unmounted when it decides what else can be unmounted,
where a chain of locked mounts ends and where a for reparenting an
overmount.&lt;/p&gt;
&lt;p&gt;clone_mnt() copies the flags of the source and only masks
MNT_INTERNAL_FLAGS which doesn&amp;#39;t include MNT_UMOUNT. A mount that was
lazily unmounted but is kept alive by a file descriptor can still be
copied when its root is an nsfs or pidfs file because may_copy_tree()
accepts those before checking whether the source is mounted at all:&lt;/p&gt;
&lt;p&gt;mount --bind /proc/self/ns/net /tmp/x
  exec 3&amp;lt; /tmp/x
  umount -l /tmp/x
  mount --bind /proc/self/fd/3 /tmp/y&lt;/p&gt;
&lt;p&gt;The mount on /tmp/y is attached to the caller&amp;#39;s namespace with
MNT_UMOUNT already set and every copy of it inherits the flag again.&lt;/p&gt;
&lt;p&gt;That causes a number of bugs:&lt;/p&gt;
&lt;p&gt;- Unlink its mountpoint from a mount namespace where it isn&amp;#39;t one.
  __detach_mounts() takes it for a mount that was unmounted earlier,
  unhooks it from its parent and drops the reference the namespace
  holds on it. It stays in the namespace with one reference too few
  and…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-53w5-4v27-r5f4</guid>
    </item>
    <item>
      <title>msrc_CVE-2026-98993 — namespace: don't inherit MNT_UMOUNT in clone_mnt()</title>
      <link>https://cve.radiocsirt.org/vuln/msrc_cve-2026-98993</link>
      <description>msrc_CVE-2026-98993</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/msrc_cve-2026-98993</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-98993</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-98993</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: don&amp;#39;t inherit MNT_UMOUNT in clone_mnt() MNT_UMOUNT gets raised on a mount that umount_tree() or umount_one() has taken out of its namespace. It&amp;#39;s never cleared. __detach_mounts() unhooks a mount that carries it instead of unmounting it. disconnect_mount() lets an unmounted child stay attached only if its parent carries it. propagate_umount() takes it as the sign that a mount is going to be unmounted when it decides what else can be unmounted, where a chain of locked mounts ends and where a for reparenting an overmount. clone_mnt() copies the flags of the source and only masks MNT_INTERNAL_FLAGS which doesn&amp;#39;t include MNT_UMOUNT. A mount that was lazily unmounted but is kept alive by a file descriptor can still be copied when its root is an nsfs or pidfs file because may_copy_tree() accepts those before checking whether the source is mounted at all:   mount --bind /proc/self/ns/net /tmp/x   exec 3&amp;lt; /tmp/x   umount -l /tmp/x   mount --bind /proc/self/fd/3 /tmp/y The mount on /tmp/y is attached to the caller&amp;#39;s namespace with MNT_UMOUNT already set and every copy of it inherits the flag again. That causes a number of bugs: - Unlink its mountpoint from a mount namespace where it isn&amp;#39;t one.   __detach_mounts() takes it for a mount that was unmounted earlier,   unhooks it from its parent and drops the reference the namespace   holds on it. It stays in the namespace with one reference too few   and as its…&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: don&amp;#39;t inherit MNT_UMOUNT in clone_mnt() MNT_UMOUNT gets raised on a mount that umount_tree() or umount_one() has taken out of its namespace. It&amp;#39;s never cleared. __detach_mounts() unhooks a mount that carries it instead of unmounting it. disconnect_mount() lets an unmounted child stay attached only if its parent carries it. propagate_umount() takes it as the sign that a mount is going to be unmounted when it decides what else can be unmounted, where a chain of locked mounts ends and where a for reparenting an overmount. clone_mnt() copies the flags of the source and only masks MNT_INTERNAL_FLAGS which doesn&amp;#39;t include MNT_UMOUNT. A mount that was lazily unmounted but is kept alive by a file descriptor can still be copied when its root is an nsfs or pidfs file because may_copy_tree() accepts those before checking whether the source is mounted at all:   mount --bind /proc/self/ns/net /tmp/x   exec 3&amp;lt; /tmp/x   umount -l /tmp/x   mount --bind /proc/self/fd/3 /tmp/y The mount on /tmp/y is attached to the caller&amp;#39;s namespace with MNT_UMOUNT already set and every copy of it inherits the flag again. That causes a number of bugs: - Unlink its mountpoint from a mount namespace where it isn&amp;#39;t one.   __detach_mounts() takes it for a mount that was unmounted earlier,   unhooks it from its parent and drops the reference the namespace   holds on it. It stays in the namespace with one reference too few   and as its…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-98993</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>
