<?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>Fri, 20 Nov 2026 21:20:46 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-99424 — ovl: set OVL_WHITEOUTS before publishing the upper dir</title>
      <link>https://db.gcve.eu/vuln/cve-2026-99424</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;ovl: set OVL_WHITEOUTS before publishing the upper dir&lt;/p&gt;
&lt;p&gt;Listing a directory while it is copied up causes a use-after-free of
the readdir cache.&lt;/p&gt;
&lt;p&gt;A merge directory must never be iterated as a real upper directory:
that mode frees the cache in OVL_I(inode)-&amp;gt;cache without looking at
its refcount, while files opened in merged mode still use it.
ovl_copy_up_workdir() publishes the upper dentry before it sets
OVL_WHITEOUTS, and ovl_dir_open() samples both without a lock, so an
open between the two stores finds the upper directory and takes it
for a real one.&lt;/p&gt;
&lt;p&gt;With a delay between the two stores, an unprivileged process that
listed a directory during its copy-up saw only &amp;#34;.&amp;#34; and &amp;#34;..&amp;#34;, and its
next getdents freed the readdir cache of another descriptor.&lt;/p&gt;
&lt;p&gt;Fix this by setting OVL_WHITEOUTS before ovl_inode_update(), so that
ovl_dir_reset() agrees with ovl_dir_open(), and by testing
OVL_TYPE_MERGE() of the path type in ovl_dir_open(), so that an open
that observes the upper dentry never iterates a merge dir as a real
dir, regardless of the order in which it observes the flag.&lt;/p&gt;
&lt;p&gt;[amir: test OVL_TYPE_MERGE() instead of smp_rmb() in ovl_dir_open()]&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;ovl: set OVL_WHITEOUTS before publishing the upper dir&lt;/p&gt;
&lt;p&gt;Listing a directory while it is copied up causes a use-after-free of
the readdir cache.&lt;/p&gt;
&lt;p&gt;A merge directory must never be iterated as a real upper directory:
that mode frees the cache in OVL_I(inode)-&amp;gt;cache without looking at
its refcount, while files opened in merged mode still use it.
ovl_copy_up_workdir() publishes the upper dentry before it sets
OVL_WHITEOUTS, and ovl_dir_open() samples both without a lock, so an
open between the two stores finds the upper directory and takes it
for a real one.&lt;/p&gt;
&lt;p&gt;With a delay between the two stores, an unprivileged process that
listed a directory during its copy-up saw only &amp;#34;.&amp;#34; and &amp;#34;..&amp;#34;, and its
next getdents freed the readdir cache of another descriptor.&lt;/p&gt;
&lt;p&gt;Fix this by setting OVL_WHITEOUTS before ovl_inode_update(), so that
ovl_dir_reset() agrees with ovl_dir_open(), and by testing
OVL_TYPE_MERGE() of the path type in ovl_dir_open(), so that an open
that observes the upper dentry never iterates a merge dir as a real
dir, regardless of the order in which it observes the flag.&lt;/p&gt;
&lt;p&gt;[amir: test OVL_TYPE_MERGE() instead of smp_rmb() in ovl_dir_open()]&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/cve-2026-99424</guid>
    </item>
  </channel>
</rss>
