<?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:37:03 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-98982 — namespace: don't let a pseudo dentry become the root of a mount</title>
      <link>https://db.gcve.eu/vuln/cve-2026-98982</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: don&amp;#39;t let a pseudo dentry become the root of a mount&lt;/p&gt;
&lt;p&gt;d_alloc_pseudo() hands out dentries for pipes, sockets and other files
that are never anyone&amp;#39;s child or parent. They carry DCACHE_NORCU and
dentry_free() frees them right away because no lockless path walk can
ever reach them. That holds as long as such a dentry isn&amp;#39;t the root of
a mount. But bind mounting /proc/self/fd/&amp;lt;fd&amp;gt; of such a file does
exactly that.&lt;/p&gt;
&lt;p&gt;Most callers of alloc_file_pseudo() put their files on kernel-internal
mounts and may_copy_tree() refuses those. bpf_token_create() doesn&amp;#39;t. It
places the token file on the bpffs mount the caller handed it and that
mount is in the caller&amp;#39;s mount namespace so the clone goes through:&lt;/p&gt;
&lt;p&gt;mount --bind /proc/self/fd/&amp;lt;token&amp;gt; &amp;lt;file&amp;gt;
  open_tree(tokfd, &amp;#34;&amp;#34;, AT_EMPTY_PATH | OPEN_TREE_CLONE) + move_mount()&lt;/p&gt;
&lt;p&gt;__follow_mount_rcu() then loads -&amp;gt;mnt_root of that mount, reads d_seq
and d_flags of the dentry and only then checks mount_lock. The dentry
can be gone by then. The final mntput() of an unmounted parent unhooks
a child that stayed attached to it under mount_lock alone. When the
child&amp;#39;s holder does the final put right after that the root is dput()
and freed immediately while a walker that found the mount hashed still
looks at it.&lt;/p&gt;
&lt;p&gt;Refuse to clone a mount with a DCACHE_NORCU dentry as its root. Nothing
sensible can be done with a bind mount of a bpf token anyway.&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: don&amp;#39;t let a pseudo dentry become the root of a mount&lt;/p&gt;
&lt;p&gt;d_alloc_pseudo() hands out dentries for pipes, sockets and other files
that are never anyone&amp;#39;s child or parent. They carry DCACHE_NORCU and
dentry_free() frees them right away because no lockless path walk can
ever reach them. That holds as long as such a dentry isn&amp;#39;t the root of
a mount. But bind mounting /proc/self/fd/&amp;lt;fd&amp;gt; of such a file does
exactly that.&lt;/p&gt;
&lt;p&gt;Most callers of alloc_file_pseudo() put their files on kernel-internal
mounts and may_copy_tree() refuses those. bpf_token_create() doesn&amp;#39;t. It
places the token file on the bpffs mount the caller handed it and that
mount is in the caller&amp;#39;s mount namespace so the clone goes through:&lt;/p&gt;
&lt;p&gt;mount --bind /proc/self/fd/&amp;lt;token&amp;gt; &amp;lt;file&amp;gt;
  open_tree(tokfd, &amp;#34;&amp;#34;, AT_EMPTY_PATH | OPEN_TREE_CLONE) + move_mount()&lt;/p&gt;
&lt;p&gt;__follow_mount_rcu() then loads -&amp;gt;mnt_root of that mount, reads d_seq
and d_flags of the dentry and only then checks mount_lock. The dentry
can be gone by then. The final mntput() of an unmounted parent unhooks
a child that stayed attached to it under mount_lock alone. When the
child&amp;#39;s holder does the final put right after that the root is dput()
and freed immediately while a walker that found the mount hashed still
looks at it.&lt;/p&gt;
&lt;p&gt;Refuse to clone a mount with a DCACHE_NORCU dentry as its root. Nothing
sensible can be done with a bind mount of a bpf token anyway.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/cve-2026-98982</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>
