<?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:32 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2026-98987</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2026-98987</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:stream: linux-lts&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:stream: linux-lts&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bell-cve-2026-98987</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-391547</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-391547</link>
      <description>EUVD-2026-391547</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-391547</guid>
    </item>
    <item>
      <title>fkie_cve-2026-98987</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-98987</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;namespace: look at the topmost mount for a mount namespace file&lt;/p&gt;
&lt;p&gt;attach_recursive_mnt() preallocates a mountpoint for the root of the
topmost mount of the source so that a mount that already sits at the
destination can be put on top of the source or on top of one of its
propagated copies.&lt;/p&gt;
&lt;p&gt;The copies are made without CL_COPY_MNT_NS_FILE so their chain of
overmounts is shorter than the source&amp;#39;s. It ends below the first bind
mount of a mount namespace file. So while the loop walks up the chain of
the source it remembers the mountpoint of that mount in &amp;#34;shorter&amp;#34; and
the existing mount is put there for the copies.&lt;/p&gt;
&lt;p&gt;But the loop ends at the topmost mount without ever looking at it. If
the topmost mount is the only mount namespace file in the chain
&amp;#34;shorter&amp;#34; stays NULL and mnt_change_mountpoint() attaches the existing
mount of the copy below the root of the mount namespace file. That&amp;#39;s a
dentry of nsfs. No path walk in the copy&amp;#39;s mount namespace ever gets
there. The mount is gone until its parent goes and the copy that took
its place can&amp;#39;t be unmounted synchronously because it has a child:&lt;/p&gt;
&lt;p&gt;S      bind mount of a file
  N      bind mount of a mount namespace file on top of S
  A      shared mount, B a slave of A, Q mounted on B/file&lt;/p&gt;
&lt;p&gt;move_mount(S, A/file)
  cat B/file          -&amp;gt; the content of S instead of Q
  umount B/file       -&amp;gt; EBUSY&lt;/p&gt;
&lt;p&gt;Look at every mount of the chain including the topmost one.&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: look at the topmost mount for a mount namespace file&lt;/p&gt;
&lt;p&gt;attach_recursive_mnt() preallocates a mountpoint for the root of the
topmost mount of the source so that a mount that already sits at the
destination can be put on top of the source or on top of one of its
propagated copies.&lt;/p&gt;
&lt;p&gt;The copies are made without CL_COPY_MNT_NS_FILE so their chain of
overmounts is shorter than the source&amp;#39;s. It ends below the first bind
mount of a mount namespace file. So while the loop walks up the chain of
the source it remembers the mountpoint of that mount in &amp;#34;shorter&amp;#34; and
the existing mount is put there for the copies.&lt;/p&gt;
&lt;p&gt;But the loop ends at the topmost mount without ever looking at it. If
the topmost mount is the only mount namespace file in the chain
&amp;#34;shorter&amp;#34; stays NULL and mnt_change_mountpoint() attaches the existing
mount of the copy below the root of the mount namespace file. That&amp;#39;s a
dentry of nsfs. No path walk in the copy&amp;#39;s mount namespace ever gets
there. The mount is gone until its parent goes and the copy that took
its place can&amp;#39;t be unmounted synchronously because it has a child:&lt;/p&gt;
&lt;p&gt;S      bind mount of a file
  N      bind mount of a mount namespace file on top of S
  A      shared mount, B a slave of A, Q mounted on B/file&lt;/p&gt;
&lt;p&gt;move_mount(S, A/file)
  cat B/file          -&amp;gt; the content of S instead of Q
  umount B/file       -&amp;gt; EBUSY&lt;/p&gt;
&lt;p&gt;Look at every mount of the chain including the topmost one.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-98987</guid>
    </item>
    <item>
      <title>GHSA-8fp8-xwh3-vf8f</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-8fp8-xwh3-vf8f</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;namespace: look at the topmost mount for a mount namespace file&lt;/p&gt;
&lt;p&gt;attach_recursive_mnt() preallocates a mountpoint for the root of the
topmost mount of the source so that a mount that already sits at the
destination can be put on top of the source or on top of one of its
propagated copies.&lt;/p&gt;
&lt;p&gt;The copies are made without CL_COPY_MNT_NS_FILE so their chain of
overmounts is shorter than the source&amp;#39;s. It ends below the first bind
mount of a mount namespace file. So while the loop walks up the chain of
the source it remembers the mountpoint of that mount in &amp;#34;shorter&amp;#34; and
the existing mount is put there for the copies.&lt;/p&gt;
&lt;p&gt;But the loop ends at the topmost mount without ever looking at it. If
the topmost mount is the only mount namespace file in the chain
&amp;#34;shorter&amp;#34; stays NULL and mnt_change_mountpoint() attaches the existing
mount of the copy below the root of the mount namespace file. That&amp;#39;s a
dentry of nsfs. No path walk in the copy&amp;#39;s mount namespace ever gets
there. The mount is gone until its parent goes and the copy that took
its place can&amp;#39;t be unmounted synchronously because it has a child:&lt;/p&gt;
&lt;p&gt;S      bind mount of a file
  N      bind mount of a mount namespace file on top of S
  A      shared mount, B a slave of A, Q mounted on B/file&lt;/p&gt;
&lt;p&gt;move_mount(S, A/file)
  cat B/file          -&amp;gt; the content of S instead of Q
  umount B/file       -&amp;gt; EBUSY&lt;/p&gt;
&lt;p&gt;Look at every mount of the chain including the topmost one.&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: look at the topmost mount for a mount namespace file&lt;/p&gt;
&lt;p&gt;attach_recursive_mnt() preallocates a mountpoint for the root of the
topmost mount of the source so that a mount that already sits at the
destination can be put on top of the source or on top of one of its
propagated copies.&lt;/p&gt;
&lt;p&gt;The copies are made without CL_COPY_MNT_NS_FILE so their chain of
overmounts is shorter than the source&amp;#39;s. It ends below the first bind
mount of a mount namespace file. So while the loop walks up the chain of
the source it remembers the mountpoint of that mount in &amp;#34;shorter&amp;#34; and
the existing mount is put there for the copies.&lt;/p&gt;
&lt;p&gt;But the loop ends at the topmost mount without ever looking at it. If
the topmost mount is the only mount namespace file in the chain
&amp;#34;shorter&amp;#34; stays NULL and mnt_change_mountpoint() attaches the existing
mount of the copy below the root of the mount namespace file. That&amp;#39;s a
dentry of nsfs. No path walk in the copy&amp;#39;s mount namespace ever gets
there. The mount is gone until its parent goes and the copy that took
its place can&amp;#39;t be unmounted synchronously because it has a child:&lt;/p&gt;
&lt;p&gt;S      bind mount of a file
  N      bind mount of a mount namespace file on top of S
  A      shared mount, B a slave of A, Q mounted on B/file&lt;/p&gt;
&lt;p&gt;move_mount(S, A/file)
  cat B/file          -&amp;gt; the content of S instead of Q
  umount B/file       -&amp;gt; EBUSY&lt;/p&gt;
&lt;p&gt;Look at every mount of the chain including the topmost one.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-8fp8-xwh3-vf8f</guid>
    </item>
    <item>
      <title>msrc_CVE-2026-98987 — namespace: look at the topmost mount for a mount namespace file</title>
      <link>https://cve.radiocsirt.org/vuln/msrc_cve-2026-98987</link>
      <description>msrc_CVE-2026-98987</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/msrc_cve-2026-98987</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-98987</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-98987</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; 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 129 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: namespace: look at the topmost mount for a mount namespace file attach_recursive_mnt() preallocates a mountpoint for the root of the topmost mount of the source so that a mount that already sits at the destination can be put on top of the source or on top of one of its propagated copies. The copies are made without CL_COPY_MNT_NS_FILE so their chain of overmounts is shorter than the source&amp;#39;s. It ends below the first bind mount of a mount namespace file. So while the loop walks up the chain of the source it remembers the mountpoint of that mount in &amp;#34;shorter&amp;#34; and the existing mount is put there for the copies. But the loop ends at the topmost mount without ever looking at it. If the topmost mount is the only mount namespace file in the chain &amp;#34;shorter&amp;#34; stays NULL and mnt_change_mountpoint() attaches the existing mount of the copy below the root of the mount namespace file. That&amp;#39;s a dentry of nsfs. No path walk in the copy&amp;#39;s mount namespace ever gets there. The mount is gone until its parent goes and the copy that took its place can&amp;#39;t be unmounted synchronously because it has a child:   S      bind mount of a file   N      bind mount of a mount namespace file on top of S   A      shared mount, B a slave of A, Q mounted on B/file   move_mount(S, A/file)   cat B/file          -&amp;gt; the content of S instead of Q   umount B/file       -&amp;gt; EBUSY Look at every mount of the chain including the topmost one.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; 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 129 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: namespace: look at the topmost mount for a mount namespace file attach_recursive_mnt() preallocates a mountpoint for the root of the topmost mount of the source so that a mount that already sits at the destination can be put on top of the source or on top of one of its propagated copies. The copies are made without CL_COPY_MNT_NS_FILE so their chain of overmounts is shorter than the source&amp;#39;s. It ends below the first bind mount of a mount namespace file. So while the loop walks up the chain of the source it remembers the mountpoint of that mount in &amp;#34;shorter&amp;#34; and the existing mount is put there for the copies. But the loop ends at the topmost mount without ever looking at it. If the topmost mount is the only mount namespace file in the chain &amp;#34;shorter&amp;#34; stays NULL and mnt_change_mountpoint() attaches the existing mount of the copy below the root of the mount namespace file. That&amp;#39;s a dentry of nsfs. No path walk in the copy&amp;#39;s mount namespace ever gets there. The mount is gone until its parent goes and the copy that took its place can&amp;#39;t be unmounted synchronously because it has a child:   S      bind mount of a file   N      bind mount of a mount namespace file on top of S   A      shared mount, B a slave of A, Q mounted on B/file   move_mount(S, A/file)   cat B/file          -&amp;gt; the content of S instead of Q   umount B/file       -&amp;gt; EBUSY Look at every mount of the chain including the topmost one.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-98987</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>
