<?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:31 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2026-98996</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2026-98996</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-98996</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-391550</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-391550</link>
      <description>EUVD-2026-391550</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-391550</guid>
    </item>
    <item>
      <title>fkie_cve-2026-98996</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-98996</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;fs: don&amp;#39;t silently unmount busy mounts&lt;/p&gt;
&lt;p&gt;The propagate_mount_busy() helper exists to decide whether a synchronous
can suceed. It does that by looking at the copies of the victims in the
mounts its parent propagates to. One of those functions from propagation
hell.&lt;/p&gt;
&lt;p&gt;It skips a copy that has child mounts except for the case of a single
child mount covering the copy&amp;#39;s root. That algorithm used to be exact.
It isn&amp;#39;t anymore.&lt;/p&gt;
&lt;p&gt;Originally only childless copies were unmounted during propagation.
And 1064f874abc0 (&amp;#34;mnt: Tuck mounts under others instead of creating
shadow/side mounts.&amp;#34;) ended up adding covered mounts to both sides in
one go.&lt;/p&gt;
&lt;p&gt;Along came 99b19d16471e (&amp;#34;mnt: In propgate_umount handle visiting mounts
in any order&amp;#34;) and that started to unmount more than before:&lt;/p&gt;
&lt;p&gt;[1]: A copy of a mount is unmounted when each of its children is either
     its overmount or a copy of the victim itself. In the former case
     the overmount gets reparented. In the latter case the copy of the
     victim will end up being unmounted.&lt;/p&gt;
&lt;p&gt;So propagate_umount() ended up being rewritten without adjusting
propagate_mount_busy(). And currently propagate_mount_busy() doesn&amp;#39;t
look at copies of the victim that have two or more children nor a single
child that is not the overmount.&lt;/p&gt;
&lt;p&gt;So any such copy in [1] is not checked for
references. The result is that a synchronous unmount succeeds, pulling
out a mount that is still in use.&lt;/p&gt;
&lt;p&gt;A contain…&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;fs: don&amp;#39;t silently unmount busy mounts&lt;/p&gt;
&lt;p&gt;The propagate_mount_busy() helper exists to decide whether a synchronous
can suceed. It does that by looking at the copies of the victims in the
mounts its parent propagates to. One of those functions from propagation
hell.&lt;/p&gt;
&lt;p&gt;It skips a copy that has child mounts except for the case of a single
child mount covering the copy&amp;#39;s root. That algorithm used to be exact.
It isn&amp;#39;t anymore.&lt;/p&gt;
&lt;p&gt;Originally only childless copies were unmounted during propagation.
And 1064f874abc0 (&amp;#34;mnt: Tuck mounts under others instead of creating
shadow/side mounts.&amp;#34;) ended up adding covered mounts to both sides in
one go.&lt;/p&gt;
&lt;p&gt;Along came 99b19d16471e (&amp;#34;mnt: In propgate_umount handle visiting mounts
in any order&amp;#34;) and that started to unmount more than before:&lt;/p&gt;
&lt;p&gt;[1]: A copy of a mount is unmounted when each of its children is either
     its overmount or a copy of the victim itself. In the former case
     the overmount gets reparented. In the latter case the copy of the
     victim will end up being unmounted.&lt;/p&gt;
&lt;p&gt;So propagate_umount() ended up being rewritten without adjusting
propagate_mount_busy(). And currently propagate_mount_busy() doesn&amp;#39;t
look at copies of the victim that have two or more children nor a single
child that is not the overmount.&lt;/p&gt;
&lt;p&gt;So any such copy in [1] is not checked for
references. The result is that a synchronous unmount succeeds, pulling
out a mount that is still in use.&lt;/p&gt;
&lt;p&gt;A contain…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-98996</guid>
    </item>
    <item>
      <title>GHSA-5j2w-v2xc-m3r3</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-5j2w-v2xc-m3r3</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;fs: don&amp;#39;t silently unmount busy mounts&lt;/p&gt;
&lt;p&gt;The propagate_mount_busy() helper exists to decide whether a synchronous
can suceed. It does that by looking at the copies of the victims in the
mounts its parent propagates to. One of those functions from propagation
hell.&lt;/p&gt;
&lt;p&gt;It skips a copy that has child mounts except for the case of a single
child mount covering the copy&amp;#39;s root. That algorithm used to be exact.
It isn&amp;#39;t anymore.&lt;/p&gt;
&lt;p&gt;Originally only childless copies were unmounted during propagation.
And 1064f874abc0 (&amp;#34;mnt: Tuck mounts under others instead of creating
shadow/side mounts.&amp;#34;) ended up adding covered mounts to both sides in
one go.&lt;/p&gt;
&lt;p&gt;Along came 99b19d16471e (&amp;#34;mnt: In propgate_umount handle visiting mounts
in any order&amp;#34;) and that started to unmount more than before:&lt;/p&gt;
&lt;p&gt;[1]: A copy of a mount is unmounted when each of its children is either
     its overmount or a copy of the victim itself. In the former case
     the overmount gets reparented. In the latter case the copy of the
     victim will end up being unmounted.&lt;/p&gt;
&lt;p&gt;So propagate_umount() ended up being rewritten without adjusting
propagate_mount_busy(). And currently propagate_mount_busy() doesn&amp;#39;t
look at copies of the victim that have two or more children nor a single
child that is not the overmount.&lt;/p&gt;
&lt;p&gt;So any such copy in [1] is not checked for
references. The result is that a synchronous unmount succeeds, pulling
out a mount that is still in use.&lt;/p&gt;
&lt;p&gt;A contain…&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;fs: don&amp;#39;t silently unmount busy mounts&lt;/p&gt;
&lt;p&gt;The propagate_mount_busy() helper exists to decide whether a synchronous
can suceed. It does that by looking at the copies of the victims in the
mounts its parent propagates to. One of those functions from propagation
hell.&lt;/p&gt;
&lt;p&gt;It skips a copy that has child mounts except for the case of a single
child mount covering the copy&amp;#39;s root. That algorithm used to be exact.
It isn&amp;#39;t anymore.&lt;/p&gt;
&lt;p&gt;Originally only childless copies were unmounted during propagation.
And 1064f874abc0 (&amp;#34;mnt: Tuck mounts under others instead of creating
shadow/side mounts.&amp;#34;) ended up adding covered mounts to both sides in
one go.&lt;/p&gt;
&lt;p&gt;Along came 99b19d16471e (&amp;#34;mnt: In propgate_umount handle visiting mounts
in any order&amp;#34;) and that started to unmount more than before:&lt;/p&gt;
&lt;p&gt;[1]: A copy of a mount is unmounted when each of its children is either
     its overmount or a copy of the victim itself. In the former case
     the overmount gets reparented. In the latter case the copy of the
     victim will end up being unmounted.&lt;/p&gt;
&lt;p&gt;So propagate_umount() ended up being rewritten without adjusting
propagate_mount_busy(). And currently propagate_mount_busy() doesn&amp;#39;t
look at copies of the victim that have two or more children nor a single
child that is not the overmount.&lt;/p&gt;
&lt;p&gt;So any such copy in [1] is not checked for
references. The result is that a synchronous unmount succeeds, pulling
out a mount that is still in use.&lt;/p&gt;
&lt;p&gt;A contain…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-5j2w-v2xc-m3r3</guid>
    </item>
    <item>
      <title>msrc_CVE-2026-98996 — fs: don't silently unmount busy mounts</title>
      <link>https://cve.radiocsirt.org/vuln/msrc_cve-2026-98996</link>
      <description>msrc_CVE-2026-98996</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/msrc_cve-2026-98996</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-98996</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-98996</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: fs: don&amp;#39;t silently unmount busy mounts The propagate_mount_busy() helper exists to decide whether a synchronous can suceed. It does that by looking at the copies of the victims in the mounts its parent propagates to. One of those functions from propagation hell. It skips a copy that has child mounts except for the case of a single child mount covering the copy&amp;#39;s root. That algorithm used to be exact. It isn&amp;#39;t anymore. Originally only childless copies were unmounted during propagation. And 1064f874abc0 (&amp;#34;mnt: Tuck mounts under others instead of creating shadow/side mounts.&amp;#34;) ended up adding covered mounts to both sides in one go. Along came 99b19d16471e (&amp;#34;mnt: In propgate_umount handle visiting mounts in any order&amp;#34;) and that started to unmount more than before: [1]: A copy of a mount is unmounted when each of its children is either      its overmount or a copy of the victim itself. In the former case      the overmount gets reparented. In the latter case the copy of the      victim will end up being unmounted. So propagate_umount() ended up being rewritten without adjusting propagate_mount_busy(). And currently propagate_mount_busy() doesn&amp;#39;t look at copies of the victim that have two or more children nor a single child that is not the overmount. So any such copy in [1] is not checked for references. The result is that a synchronous unmount succeeds, pulling out a mount that is still in use. A container can ru…&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: fs: don&amp;#39;t silently unmount busy mounts The propagate_mount_busy() helper exists to decide whether a synchronous can suceed. It does that by looking at the copies of the victims in the mounts its parent propagates to. One of those functions from propagation hell. It skips a copy that has child mounts except for the case of a single child mount covering the copy&amp;#39;s root. That algorithm used to be exact. It isn&amp;#39;t anymore. Originally only childless copies were unmounted during propagation. And 1064f874abc0 (&amp;#34;mnt: Tuck mounts under others instead of creating shadow/side mounts.&amp;#34;) ended up adding covered mounts to both sides in one go. Along came 99b19d16471e (&amp;#34;mnt: In propgate_umount handle visiting mounts in any order&amp;#34;) and that started to unmount more than before: [1]: A copy of a mount is unmounted when each of its children is either      its overmount or a copy of the victim itself. In the former case      the overmount gets reparented. In the latter case the copy of the      victim will end up being unmounted. So propagate_umount() ended up being rewritten without adjusting propagate_mount_busy(). And currently propagate_mount_busy() doesn&amp;#39;t look at copies of the victim that have two or more children nor a single child that is not the overmount. So any such copy in [1] is not checked for references. The result is that a synchronous unmount succeeds, pulling out a mount that is still in use. A container can ru…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-98996</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>
