<?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://db.gcve.eu</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>Wed, 11 Nov 2026 18:17:40 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-98996 — fs: don't silently unmount busy mounts</title>
      <link>https://db.gcve.eu/vuln/cve-2026-98996</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&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;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&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://db.gcve.eu/vuln/cve-2026-98996</guid>
    </item>
    <item>
      <title>USN-9018-1 — linux, linux-aws, linux-gcp, linux-ibm, linux-oem-7.0, linux-oracle vulnerabilities</title>
      <link>https://db.gcve.eu/vuln/usn-9018-1</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:26.04:LTS: linux, Ubuntu:26.04:LTS: linux-aws, Ubuntu:26.04:LTS: linux-gcp, Ubuntu:26.04:LTS: linux-ibm, Ubuntu:26.04:LTS: linux-oem-7.0, Ubuntu:26.04:LTS: linux-oracle&lt;/p&gt;
&lt;p&gt;Several security issues were discovered in the Linux kernel.
An attacker could possibly use these to compromise the system.
This update corrects flaws in the following subsystems:
  - Network file systems library;
  - Stream parser;
  - ARM64 architecture;
  - PowerPC architecture;
  - RISC-V architecture;
  - S390 architecture;
  - User-Mode Linux (UML);
  - x86 architecture;
  - Block layer subsystem;
  - Android drivers;
  - Bluetooth drivers;
  - TPM device driver;
  - DPLL subsystem;
  - EDAC drivers;
  - GPIO subsystem;
  - GPU drivers;
  - HID subsystem;
  - IIO subsystem;
  - IIO ADC drivers;
  - InfiniBand drivers;
  - Input Device (Miscellaneous) drivers;
  - Multiple devices driver;
  - MemoryStick subsystem;
  - MMC subsystem;
  - MTD block device drivers;
  - Network drivers;
  - Ethernet bonding driver;
  - Mellanox network drivers;
  - STMicroelectronics network drivers;
  - Ethernet team driver;
  - MediaTek network drivers;
  - NVME drivers;
  - Device tree and open firmware driver;
  - Power sequencing drivers;
  - Voltage and Current Regulator drivers;
  - Real Time Clock drivers;
  - SCSI subsystem;
  - Greybus lights staging drivers;
  - Trusted Execution Environment drivers;
  - Thunderbolt and USB4 drivers;
  - TTY drivers;
  - Cadence USB3 driver;
  - USB Device Class drivers;
  - USB core drivers;
  - DesignWare USB2 driver;
  - DesignWare USB3 driver;
  - USB Gadget drivers;
  - USB Serial drivers;
  - USB Mass Storage drivers;
  - USB Type-C suppor…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:26.04:LTS: linux, Ubuntu:26.04:LTS: linux-aws, Ubuntu:26.04:LTS: linux-gcp, Ubuntu:26.04:LTS: linux-ibm, Ubuntu:26.04:LTS: linux-oem-7.0, Ubuntu:26.04:LTS: linux-oracle&lt;/p&gt;
&lt;p&gt;Several security issues were discovered in the Linux kernel.
An attacker could possibly use these to compromise the system.
This update corrects flaws in the following subsystems:
  - Network file systems library;
  - Stream parser;
  - ARM64 architecture;
  - PowerPC architecture;
  - RISC-V architecture;
  - S390 architecture;
  - User-Mode Linux (UML);
  - x86 architecture;
  - Block layer subsystem;
  - Android drivers;
  - Bluetooth drivers;
  - TPM device driver;
  - DPLL subsystem;
  - EDAC drivers;
  - GPIO subsystem;
  - GPU drivers;
  - HID subsystem;
  - IIO subsystem;
  - IIO ADC drivers;
  - InfiniBand drivers;
  - Input Device (Miscellaneous) drivers;
  - Multiple devices driver;
  - MemoryStick subsystem;
  - MMC subsystem;
  - MTD block device drivers;
  - Network drivers;
  - Ethernet bonding driver;
  - Mellanox network drivers;
  - STMicroelectronics network drivers;
  - Ethernet team driver;
  - MediaTek network drivers;
  - NVME drivers;
  - Device tree and open firmware driver;
  - Power sequencing drivers;
  - Voltage and Current Regulator drivers;
  - Real Time Clock drivers;
  - SCSI subsystem;
  - Greybus lights staging drivers;
  - Trusted Execution Environment drivers;
  - Thunderbolt and USB4 drivers;
  - TTY drivers;
  - Cadence USB3 driver;
  - USB Device Class drivers;
  - USB core drivers;
  - DesignWare USB2 driver;
  - DesignWare USB3 driver;
  - USB Gadget drivers;
  - USB Serial drivers;
  - USB Mass Storage drivers;
  - USB Type-C suppor…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/usn-9018-1</guid>
    </item>
  </channel>
</rss>
