<?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 16:47:23 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-98977 — namespace: handle mount locking for automounts correctly</title>
      <link>https://db.gcve.eu/vuln/cve-2026-98977</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;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;&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;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://db.gcve.eu/vuln/cve-2026-98977</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>
