<?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>Tue, 10 Nov 2026 01:02:46 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-99172</title>
      <link>https://db.gcve.eu/vuln/fkie_cve-2026-99172</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;ipc: drop the mqueue mount with kern_unmount() on setup failure&lt;/p&gt;
&lt;p&gt;mq_init_ns() creates the mqueue mount with fc_mount_longterm(), so its
-&amp;gt;mnt_ns is MNT_NS_INTERNAL. When setting up the mqueue or ipc sysctls
or msg_init_ns() fails afterwards, create_ipc_ns() drops it with a plain
mntput(). With -&amp;gt;mnt_ns set that takes the fast path of
mntput_no_expire(). The count drops to zero and nothing ever kills the
mount, so the mount and the mqueue superblock are leaked.&lt;/p&gt;
&lt;p&gt;Commit dc55e35f9e81 (&amp;#34;ipc: Store mqueue sysctls in the ipc namespace&amp;#34;)
added the first failure path after mq_init_ns() and never dropped the
mount. Commit 7229d74e5e8c (&amp;#34;ipc: create_ipc_ns: drop mqueue mount on
sysctl setup failure&amp;#34;) tried to fix that with a mntput() but that
doesn&amp;#39;t help for a long-term mount.&lt;/p&gt;
&lt;p&gt;Use kern_unmount(). free_ipc() open-codes the same thing for a namespace
that made it.&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;ipc: drop the mqueue mount with kern_unmount() on setup failure&lt;/p&gt;
&lt;p&gt;mq_init_ns() creates the mqueue mount with fc_mount_longterm(), so its
-&amp;gt;mnt_ns is MNT_NS_INTERNAL. When setting up the mqueue or ipc sysctls
or msg_init_ns() fails afterwards, create_ipc_ns() drops it with a plain
mntput(). With -&amp;gt;mnt_ns set that takes the fast path of
mntput_no_expire(). The count drops to zero and nothing ever kills the
mount, so the mount and the mqueue superblock are leaked.&lt;/p&gt;
&lt;p&gt;Commit dc55e35f9e81 (&amp;#34;ipc: Store mqueue sysctls in the ipc namespace&amp;#34;)
added the first failure path after mq_init_ns() and never dropped the
mount. Commit 7229d74e5e8c (&amp;#34;ipc: create_ipc_ns: drop mqueue mount on
sysctl setup failure&amp;#34;) tried to fix that with a mntput() but that
doesn&amp;#39;t help for a long-term mount.&lt;/p&gt;
&lt;p&gt;Use kern_unmount(). free_ipc() open-codes the same thing for a namespace
that made it.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/fkie_cve-2026-99172</guid>
    </item>
    <item>
      <title>GHSA-c64w-44gc-4h7w</title>
      <link>https://db.gcve.eu/vuln/ghsa-c64w-44gc-4h7w</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;ipc: drop the mqueue mount with kern_unmount() on setup failure&lt;/p&gt;
&lt;p&gt;mq_init_ns() creates the mqueue mount with fc_mount_longterm(), so its
-&amp;gt;mnt_ns is MNT_NS_INTERNAL. When setting up the mqueue or ipc sysctls
or msg_init_ns() fails afterwards, create_ipc_ns() drops it with a plain
mntput(). With -&amp;gt;mnt_ns set that takes the fast path of
mntput_no_expire(). The count drops to zero and nothing ever kills the
mount, so the mount and the mqueue superblock are leaked.&lt;/p&gt;
&lt;p&gt;Commit dc55e35f9e81 (&amp;#34;ipc: Store mqueue sysctls in the ipc namespace&amp;#34;)
added the first failure path after mq_init_ns() and never dropped the
mount. Commit 7229d74e5e8c (&amp;#34;ipc: create_ipc_ns: drop mqueue mount on
sysctl setup failure&amp;#34;) tried to fix that with a mntput() but that
doesn&amp;#39;t help for a long-term mount.&lt;/p&gt;
&lt;p&gt;Use kern_unmount(). free_ipc() open-codes the same thing for a namespace
that made it.&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;ipc: drop the mqueue mount with kern_unmount() on setup failure&lt;/p&gt;
&lt;p&gt;mq_init_ns() creates the mqueue mount with fc_mount_longterm(), so its
-&amp;gt;mnt_ns is MNT_NS_INTERNAL. When setting up the mqueue or ipc sysctls
or msg_init_ns() fails afterwards, create_ipc_ns() drops it with a plain
mntput(). With -&amp;gt;mnt_ns set that takes the fast path of
mntput_no_expire(). The count drops to zero and nothing ever kills the
mount, so the mount and the mqueue superblock are leaked.&lt;/p&gt;
&lt;p&gt;Commit dc55e35f9e81 (&amp;#34;ipc: Store mqueue sysctls in the ipc namespace&amp;#34;)
added the first failure path after mq_init_ns() and never dropped the
mount. Commit 7229d74e5e8c (&amp;#34;ipc: create_ipc_ns: drop mqueue mount on
sysctl setup failure&amp;#34;) tried to fix that with a mntput() but that
doesn&amp;#39;t help for a long-term mount.&lt;/p&gt;
&lt;p&gt;Use kern_unmount(). free_ipc() open-codes the same thing for a namespace
that made it.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ghsa-c64w-44gc-4h7w</guid>
    </item>
    <item>
      <title>msrc_CVE-2026-99172 — ipc: drop the mqueue mount with kern_unmount() on setup failure</title>
      <link>https://db.gcve.eu/vuln/msrc_cve-2026-99172</link>
      <description>msrc_CVE-2026-99172</description>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/msrc_cve-2026-99172</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-99172</title>
      <link>https://db.gcve.eu/vuln/ubuntu-cve-2026-99172</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 199 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: ipc: drop the mqueue mount with kern_unmount() on setup failure mq_init_ns() creates the mqueue mount with fc_mount_longterm(), so its -&amp;gt;mnt_ns is MNT_NS_INTERNAL. When setting up the mqueue or ipc sysctls or msg_init_ns() fails afterwards, create_ipc_ns() drops it with a plain mntput(). With -&amp;gt;mnt_ns set that takes the fast path of mntput_no_expire(). The count drops to zero and nothing ever kills the mount, so the mount and the mqueue superblock are leaked. Commit dc55e35f9e81 (&amp;#34;ipc: Store mqueue sysctls in the ipc namespace&amp;#34;) added the first failure path after mq_init_ns() and never dropped the mount. Commit 7229d74e5e8c (&amp;#34;ipc: create_ipc_ns: drop mqueue mount on sysctl setup failure&amp;#34;) tried to fix that with a mntput() but that doesn&amp;#39;t help for a long-term mount. Use kern_unmount(). free_ipc() open-codes the same thing for a namespace that made it.&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 199 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: ipc: drop the mqueue mount with kern_unmount() on setup failure mq_init_ns() creates the mqueue mount with fc_mount_longterm(), so its -&amp;gt;mnt_ns is MNT_NS_INTERNAL. When setting up the mqueue or ipc sysctls or msg_init_ns() fails afterwards, create_ipc_ns() drops it with a plain mntput(). With -&amp;gt;mnt_ns set that takes the fast path of mntput_no_expire(). The count drops to zero and nothing ever kills the mount, so the mount and the mqueue superblock are leaked. Commit dc55e35f9e81 (&amp;#34;ipc: Store mqueue sysctls in the ipc namespace&amp;#34;) added the first failure path after mq_init_ns() and never dropped the mount. Commit 7229d74e5e8c (&amp;#34;ipc: create_ipc_ns: drop mqueue mount on sysctl setup failure&amp;#34;) tried to fix that with a mntput() but that doesn&amp;#39;t help for a long-term mount. Use kern_unmount(). free_ipc() open-codes the same thing for a namespace that made it.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ubuntu-cve-2026-99172</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-4224 — Linux Kernel: Mehrere Schwachstellen ermöglichen nicht spezifizierten Angriff</title>
      <link>https://db.gcve.eu/vuln/wid-sec-w-2026-4224</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://db.gcve.eu/vuln/wid-sec-w-2026-4224</guid>
    </item>
  </channel>
</rss>
