<?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:15 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-99641 — ovl: fail the mount if the casefold flag has changed</title>
      <link>https://db.gcve.eu/vuln/cve-2026-99641</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: fail the mount if the casefold flag has changed&lt;/p&gt;
&lt;p&gt;An unprivileged user in a user namespace can repeatedly trigger a kernel
warning with their own overlay mounts. They do so by changing the
casefold flag of the topmost layer&amp;#39;s empty root, the top directory of
that layer, after the layers are set and before the mount is created.&lt;/p&gt;
&lt;p&gt;The casefold flag of a directory makes name lookups in that directory
case-insensitive. All layers of an overlay must agree on casefolding.&lt;/p&gt;
&lt;p&gt;ovl_mount_dir_check() reads the casefold flag of a layer root when
fsconfig() sets that layer, and saves the result in ofs-&amp;gt;casefold. The
mount is created later, by another fsconfig() call with
FSCONFIG_CMD_CREATE.&lt;/p&gt;
&lt;p&gt;The casefold flag of an empty directory can be changed.&lt;/p&gt;
&lt;p&gt;The casefold flag of the overlay root must match ofs-&amp;gt;casefold.
ovl_get_root() copies the flag from the topmost layer root, as it is
when the mount is created. On a mismatch, ovl_get_root() only does a
WARN_ON(), and the mount continues. The check is not a WARN_ON_ONCE(),
so each such mount warns again.&lt;/p&gt;
&lt;p&gt;An unprivileged user needs CONFIG_UNICODE, and a tmpfs mounted with the
casefold option in their namespace.&lt;/p&gt;
&lt;p&gt;Reproduced by changing the casefold flag of the empty upper directory
after the layers were set and before FSCONFIG_CMD_CREATE, with tmpfs and
ext4 layers, and as uid 1000 in a user namespace.&lt;/p&gt;
&lt;p&gt;Fix this by replacing the WARN_ON() with a check that fails the mount
wit…&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: fail the mount if the casefold flag has changed&lt;/p&gt;
&lt;p&gt;An unprivileged user in a user namespace can repeatedly trigger a kernel
warning with their own overlay mounts. They do so by changing the
casefold flag of the topmost layer&amp;#39;s empty root, the top directory of
that layer, after the layers are set and before the mount is created.&lt;/p&gt;
&lt;p&gt;The casefold flag of a directory makes name lookups in that directory
case-insensitive. All layers of an overlay must agree on casefolding.&lt;/p&gt;
&lt;p&gt;ovl_mount_dir_check() reads the casefold flag of a layer root when
fsconfig() sets that layer, and saves the result in ofs-&amp;gt;casefold. The
mount is created later, by another fsconfig() call with
FSCONFIG_CMD_CREATE.&lt;/p&gt;
&lt;p&gt;The casefold flag of an empty directory can be changed.&lt;/p&gt;
&lt;p&gt;The casefold flag of the overlay root must match ofs-&amp;gt;casefold.
ovl_get_root() copies the flag from the topmost layer root, as it is
when the mount is created. On a mismatch, ovl_get_root() only does a
WARN_ON(), and the mount continues. The check is not a WARN_ON_ONCE(),
so each such mount warns again.&lt;/p&gt;
&lt;p&gt;An unprivileged user needs CONFIG_UNICODE, and a tmpfs mounted with the
casefold option in their namespace.&lt;/p&gt;
&lt;p&gt;Reproduced by changing the casefold flag of the empty upper directory
after the layers were set and before FSCONFIG_CMD_CREATE, with tmpfs and
ext4 layers, and as uid 1000 in a user namespace.&lt;/p&gt;
&lt;p&gt;Fix this by replacing the WARN_ON() with a check that fails the mount
wit…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/cve-2026-99641</guid>
    </item>
  </channel>
</rss>
