<?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:09:55 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2026-98977</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2026-98977</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-98977</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-396111</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-396111</link>
      <description>EUVD-2026-396111</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-396111</guid>
    </item>
    <item>
      <title>fkie_cve-2026-98977</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-98977</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;namespace: handle mount locking for automounts correctly&lt;/p&gt;
&lt;p&gt;If mounts are propagated across user namespaces, attach_recursive_mnt()
locks every copy of the source mount to protect overmounts from
vanishing and revealing the underlying files or directories.&lt;/p&gt;
&lt;p&gt;The user namespace is taken from the caller&amp;#39;s mount namespaces since
this is where the mounts end up. Except, that&amp;#39;s not always true.
Automounts may legitimately get popped in by tasks located in a
different mount and user namespace during path lookup.&lt;/p&gt;
&lt;p&gt;Then check doesn&amp;#39;t make sense at that point. The copy in the namespace
of the parent - which may be the host&amp;#39;s - is now locked and the host
cannot change the flags of its own mounts anymore.&lt;/p&gt;
&lt;p&gt;Here&amp;#39;s the reproducer:&lt;/p&gt;
&lt;p&gt;- host has debugfs mounted nosuid,nodev,noexec and shared
- tracefs automount below it is not yet active
- hand a child process a directory descriptor on that mount
- child process enters auser and mount namespace
- child process&amp;#39; namespace now holds a locked copy of the host&amp;#39;s debugfs
  mount that receives propagation from it
- child process stats &amp;#34;tracing/.&amp;#34; through the descriptor
- lookup runs on the host&amp;#39;s mount so the automount lands below the host&amp;#39;s mount
- propagation puts a copy below the child&amp;#39;s copy
- both try to clear the flags on the mount they got, with a bind remount:&lt;/p&gt;
&lt;p&gt;host, on its own automount:            MS_REMOUNT|MS_BIND = EPERM
    child, on the copy in its namespace:   M…&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: handle mount locking for automounts correctly&lt;/p&gt;
&lt;p&gt;If mounts are propagated across user namespaces, attach_recursive_mnt()
locks every copy of the source mount to protect overmounts from
vanishing and revealing the underlying files or directories.&lt;/p&gt;
&lt;p&gt;The user namespace is taken from the caller&amp;#39;s mount namespaces since
this is where the mounts end up. Except, that&amp;#39;s not always true.
Automounts may legitimately get popped in by tasks located in a
different mount and user namespace during path lookup.&lt;/p&gt;
&lt;p&gt;Then check doesn&amp;#39;t make sense at that point. The copy in the namespace
of the parent - which may be the host&amp;#39;s - is now locked and the host
cannot change the flags of its own mounts anymore.&lt;/p&gt;
&lt;p&gt;Here&amp;#39;s the reproducer:&lt;/p&gt;
&lt;p&gt;- host has debugfs mounted nosuid,nodev,noexec and shared
- tracefs automount below it is not yet active
- hand a child process a directory descriptor on that mount
- child process enters auser and mount namespace
- child process&amp;#39; namespace now holds a locked copy of the host&amp;#39;s debugfs
  mount that receives propagation from it
- child process stats &amp;#34;tracing/.&amp;#34; through the descriptor
- lookup runs on the host&amp;#39;s mount so the automount lands below the host&amp;#39;s mount
- propagation puts a copy below the child&amp;#39;s copy
- both try to clear the flags on the mount they got, with a bind remount:&lt;/p&gt;
&lt;p&gt;host, on its own automount:            MS_REMOUNT|MS_BIND = EPERM
    child, on the copy in its namespace:   M…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-98977</guid>
    </item>
    <item>
      <title>GHSA-qrj7-g2h3-853j</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-qrj7-g2h3-853j</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;namespace: handle mount locking for automounts correctly&lt;/p&gt;
&lt;p&gt;If mounts are propagated across user namespaces, attach_recursive_mnt()
locks every copy of the source mount to protect overmounts from
vanishing and revealing the underlying files or directories.&lt;/p&gt;
&lt;p&gt;The user namespace is taken from the caller&amp;#39;s mount namespaces since
this is where the mounts end up. Except, that&amp;#39;s not always true.
Automounts may legitimately get popped in by tasks located in a
different mount and user namespace during path lookup.&lt;/p&gt;
&lt;p&gt;Then check doesn&amp;#39;t make sense at that point. The copy in the namespace
of the parent - which may be the host&amp;#39;s - is now locked and the host
cannot change the flags of its own mounts anymore.&lt;/p&gt;
&lt;p&gt;Here&amp;#39;s the reproducer:&lt;/p&gt;
&lt;p&gt;- host has debugfs mounted nosuid,nodev,noexec and shared
- tracefs automount below it is not yet active
- hand a child process a directory descriptor on that mount
- child process enters auser and mount namespace
- child process&amp;#39; namespace now holds a locked copy of the host&amp;#39;s debugfs
  mount that receives propagation from it
- child process stats &amp;#34;tracing/.&amp;#34; through the descriptor
- lookup runs on the host&amp;#39;s mount so the automount lands below the host&amp;#39;s mount
- propagation puts a copy below the child&amp;#39;s copy
- both try to clear the flags on the mount they got, with a bind remount:&lt;/p&gt;
&lt;p&gt;host, on its own automount:            MS_REMOUNT|MS_BIND = EPERM
    child, on the copy in its namespace:   M…&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: handle mount locking for automounts correctly&lt;/p&gt;
&lt;p&gt;If mounts are propagated across user namespaces, attach_recursive_mnt()
locks every copy of the source mount to protect overmounts from
vanishing and revealing the underlying files or directories.&lt;/p&gt;
&lt;p&gt;The user namespace is taken from the caller&amp;#39;s mount namespaces since
this is where the mounts end up. Except, that&amp;#39;s not always true.
Automounts may legitimately get popped in by tasks located in a
different mount and user namespace during path lookup.&lt;/p&gt;
&lt;p&gt;Then check doesn&amp;#39;t make sense at that point. The copy in the namespace
of the parent - which may be the host&amp;#39;s - is now locked and the host
cannot change the flags of its own mounts anymore.&lt;/p&gt;
&lt;p&gt;Here&amp;#39;s the reproducer:&lt;/p&gt;
&lt;p&gt;- host has debugfs mounted nosuid,nodev,noexec and shared
- tracefs automount below it is not yet active
- hand a child process a directory descriptor on that mount
- child process enters auser and mount namespace
- child process&amp;#39; namespace now holds a locked copy of the host&amp;#39;s debugfs
  mount that receives propagation from it
- child process stats &amp;#34;tracing/.&amp;#34; through the descriptor
- lookup runs on the host&amp;#39;s mount so the automount lands below the host&amp;#39;s mount
- propagation puts a copy below the child&amp;#39;s copy
- both try to clear the flags on the mount they got, with a bind remount:&lt;/p&gt;
&lt;p&gt;host, on its own automount:            MS_REMOUNT|MS_BIND = EPERM
    child, on the copy in its namespace:   M…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-qrj7-g2h3-853j</guid>
    </item>
    <item>
      <title>msrc_CVE-2026-98977 — namespace: handle mount locking for automounts correctly</title>
      <link>https://cve.radiocsirt.org/vuln/msrc_cve-2026-98977</link>
      <description>msrc_CVE-2026-98977</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/msrc_cve-2026-98977</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-98977</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-98977</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux, 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 and 257 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: namespace: handle mount locking for automounts correctly If mounts are propagated across user namespaces, attach_recursive_mnt() locks every copy of the source mount to protect overmounts from vanishing and revealing the underlying files or directories. The user namespace is taken from the caller&amp;#39;s mount namespaces since this is where the mounts end up. Except, that&amp;#39;s not always true. Automounts may legitimately get popped in by tasks located in a different mount and user namespace during path lookup. Then check doesn&amp;#39;t make sense at that point. The copy in the namespace of the parent - which may be the host&amp;#39;s - is now locked and the host cannot change the flags of its own mounts anymore. Here&amp;#39;s the reproducer: - host has debugfs mounted nosuid,nodev,noexec and shared - tracefs automount below it is not yet active - hand a child process a directory descriptor on that mount - child process enters auser and mount namespace - child process&amp;#39; namespace now holds a locked copy of the host&amp;#39;s debugfs   mount that receives propagation from it - child process stats &amp;#34;tracing/.&amp;#34; through the descriptor - lookup runs on the host&amp;#39;s mount so the automount lands below the host&amp;#39;s mount - propagation puts a copy below the child&amp;#39;s copy - both try to clear the flags on the mount they got, with a bind remount:     host, on its own automount:            MS_REMOUNT|MS_BIND = EPERM     child, on the copy in its namespace:   MS_REMOU…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux, 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 and 257 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: namespace: handle mount locking for automounts correctly If mounts are propagated across user namespaces, attach_recursive_mnt() locks every copy of the source mount to protect overmounts from vanishing and revealing the underlying files or directories. The user namespace is taken from the caller&amp;#39;s mount namespaces since this is where the mounts end up. Except, that&amp;#39;s not always true. Automounts may legitimately get popped in by tasks located in a different mount and user namespace during path lookup. Then check doesn&amp;#39;t make sense at that point. The copy in the namespace of the parent - which may be the host&amp;#39;s - is now locked and the host cannot change the flags of its own mounts anymore. Here&amp;#39;s the reproducer: - host has debugfs mounted nosuid,nodev,noexec and shared - tracefs automount below it is not yet active - hand a child process a directory descriptor on that mount - child process enters auser and mount namespace - child process&amp;#39; namespace now holds a locked copy of the host&amp;#39;s debugfs   mount that receives propagation from it - child process stats &amp;#34;tracing/.&amp;#34; through the descriptor - lookup runs on the host&amp;#39;s mount so the automount lands below the host&amp;#39;s mount - propagation puts a copy below the child&amp;#39;s copy - both try to clear the flags on the mount they got, with a bind remount:     host, on its own automount:            MS_REMOUNT|MS_BIND = EPERM     child, on the copy in its namespace:   MS_REMOU…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-98977</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>
