<?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://vulnerability.circl.lu</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>Thu, 01 Oct 2026 23:24:56 +0000</lastBuildDate>
    <item>
      <title>CVE-2022-50280 — pnode: terminate at peers of source</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2022-50280</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;pnode: terminate at peers of source&lt;/p&gt;
&lt;p&gt;The propagate_mnt() function handles mount propagation when creating
mounts and propagates the source mount tree @source_mnt to all
applicable nodes of the destination propagation mount tree headed by
@dest_mnt.&lt;/p&gt;
&lt;p&gt;Unfortunately it contains a bug where it fails to terminate at peers of
@source_mnt when looking up copies of the source mount that become
masters for copies of the source mount tree mounted on top of slaves in
the destination propagation tree causing a NULL dereference.&lt;/p&gt;
&lt;p&gt;Once the mechanics of the bug are understood it&amp;#39;s easy to trigger.
Because of unprivileged user namespaces it is available to unprivileged
users.&lt;/p&gt;
&lt;p&gt;While fixing this bug we&amp;#39;ve gotten confused multiple times due to
unclear terminology or missing concepts. So let&amp;#39;s start this with some
clarifications:&lt;/p&gt;
&lt;p&gt;* The terms &amp;#34;master&amp;#34; or &amp;#34;peer&amp;#34; denote a shared mount. A shared mount
  belongs to a peer group.&lt;/p&gt;
&lt;p&gt;* A peer group is a set of shared mounts that propagate to each other.
  They are identified by a peer group id. The peer group id is available
  in @shared_mnt-&amp;gt;mnt_group_id.
  Shared mounts within the same peer group have the same peer group id.
  The peers in a peer group can be reached via @shared_mnt-&amp;gt;mnt_share.&lt;/p&gt;
&lt;p&gt;* The terms &amp;#34;slave mount&amp;#34; or &amp;#34;dependent mount&amp;#34; denote a mount that
  receives propagation from a peer in a peer group. IOW, shared mounts
  may have slave mounts and slave mounts have share…&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;pnode: terminate at peers of source&lt;/p&gt;
&lt;p&gt;The propagate_mnt() function handles mount propagation when creating
mounts and propagates the source mount tree @source_mnt to all
applicable nodes of the destination propagation mount tree headed by
@dest_mnt.&lt;/p&gt;
&lt;p&gt;Unfortunately it contains a bug where it fails to terminate at peers of
@source_mnt when looking up copies of the source mount that become
masters for copies of the source mount tree mounted on top of slaves in
the destination propagation tree causing a NULL dereference.&lt;/p&gt;
&lt;p&gt;Once the mechanics of the bug are understood it&amp;#39;s easy to trigger.
Because of unprivileged user namespaces it is available to unprivileged
users.&lt;/p&gt;
&lt;p&gt;While fixing this bug we&amp;#39;ve gotten confused multiple times due to
unclear terminology or missing concepts. So let&amp;#39;s start this with some
clarifications:&lt;/p&gt;
&lt;p&gt;* The terms &amp;#34;master&amp;#34; or &amp;#34;peer&amp;#34; denote a shared mount. A shared mount
  belongs to a peer group.&lt;/p&gt;
&lt;p&gt;* A peer group is a set of shared mounts that propagate to each other.
  They are identified by a peer group id. The peer group id is available
  in @shared_mnt-&amp;gt;mnt_group_id.
  Shared mounts within the same peer group have the same peer group id.
  The peers in a peer group can be reached via @shared_mnt-&amp;gt;mnt_share.&lt;/p&gt;
&lt;p&gt;* The terms &amp;#34;slave mount&amp;#34; or &amp;#34;dependent mount&amp;#34; denote a mount that
  receives propagation from a peer in a peer group. IOW, shared mounts
  may have slave mounts and slave mounts have share…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2022-50280</guid>
    </item>
  </channel>
</rss>
