<?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:23:12 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-99420 — ovl: check that the parents of volatile/dirty are dirs</title>
      <link>https://db.gcve.eu/vuln/cve-2026-99420</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: check that the parents of volatile/dirty are dirs&lt;/p&gt;
&lt;p&gt;An unprivileged user crashes the kernel by mounting overlayfs with the
volatile option.&lt;/p&gt;
&lt;p&gt;A dentry that serves as the parent of a lookup must be a directory.
ovl_create_volatile_dirty() walks work/incompat/volatile/dirty by name,
and ovl_lookup_or_create() returns an existing entry whatever its type.
A file or a symlink that another task creates during the mount becomes
the parent of the next lookup, which calls a NULL -&amp;gt;lookup.&lt;/p&gt;
&lt;p&gt;An unprivileged user mounted overlayfs with &amp;#34;volatile&amp;#34; in a user
namespace while a second process created a symlink named work/incompat,
and the mount task oopsed on a NULL -&amp;gt;lookup call.&lt;/p&gt;
&lt;p&gt;Fix this by returning -ENOTDIR from ovl_lookup_or_create() when the
caller asked for a directory and the existing entry is a non-dir.&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: check that the parents of volatile/dirty are dirs&lt;/p&gt;
&lt;p&gt;An unprivileged user crashes the kernel by mounting overlayfs with the
volatile option.&lt;/p&gt;
&lt;p&gt;A dentry that serves as the parent of a lookup must be a directory.
ovl_create_volatile_dirty() walks work/incompat/volatile/dirty by name,
and ovl_lookup_or_create() returns an existing entry whatever its type.
A file or a symlink that another task creates during the mount becomes
the parent of the next lookup, which calls a NULL -&amp;gt;lookup.&lt;/p&gt;
&lt;p&gt;An unprivileged user mounted overlayfs with &amp;#34;volatile&amp;#34; in a user
namespace while a second process created a symlink named work/incompat,
and the mount task oopsed on a NULL -&amp;gt;lookup call.&lt;/p&gt;
&lt;p&gt;Fix this by returning -ENOTDIR from ovl_lookup_or_create() when the
caller asked for a directory and the existing entry is a non-dir.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/cve-2026-99420</guid>
    </item>
  </channel>
</rss>
