<?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 19:53:18 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-68149 — fs: preserve ACL_DONT_CACHE state in forget_cached_acl()</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-68149</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;fs: preserve ACL_DONT_CACHE state in forget_cached_acl()&lt;/p&gt;
&lt;p&gt;The ACL_DONT_CACHE state is meant to be a constant state for the inode
for filesystems that want to opt out of posix acl caching.&lt;/p&gt;
&lt;p&gt;Commit facd61053cff1 (&amp;#34;fuse: fixes after adapting to new posix acl api&amp;#34;)
used this facility to opt out of posix acl caching for fuse inodes with
fuse server that does not negotiate FUSE_POSIX_ACL (fc-&amp;gt;posix_acl).&lt;/p&gt;
&lt;p&gt;The commit also takes care to gate the forget_all_cached_acls() call in
fuse_set_acl() on fc-&amp;gt;posix_acl because there is no need for it, but
there are other placed in fuse code which call forget_all_cached_acls()
unconditional to fc-&amp;gt;posix_acl and those cause the loss of the
ACL_DONT_CACHE state.&lt;/p&gt;
&lt;p&gt;This is not only a functional bug. Properly timed, a get_acl() from this
fuse filesystem can return a stale cached value, as was observed in tests,
because set_acl() does not invalidate the unintentional acl cache.&lt;/p&gt;
&lt;p&gt;We could fix this in fuse, but it actually makes no sense for the vfs
helper forget_cached_acl() to invalidate the ACL_DONT_CACHE state, so
let it not do that to fix fuse and future users of ACL_DONT_CACHE.&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;fs: preserve ACL_DONT_CACHE state in forget_cached_acl()&lt;/p&gt;
&lt;p&gt;The ACL_DONT_CACHE state is meant to be a constant state for the inode
for filesystems that want to opt out of posix acl caching.&lt;/p&gt;
&lt;p&gt;Commit facd61053cff1 (&amp;#34;fuse: fixes after adapting to new posix acl api&amp;#34;)
used this facility to opt out of posix acl caching for fuse inodes with
fuse server that does not negotiate FUSE_POSIX_ACL (fc-&amp;gt;posix_acl).&lt;/p&gt;
&lt;p&gt;The commit also takes care to gate the forget_all_cached_acls() call in
fuse_set_acl() on fc-&amp;gt;posix_acl because there is no need for it, but
there are other placed in fuse code which call forget_all_cached_acls()
unconditional to fc-&amp;gt;posix_acl and those cause the loss of the
ACL_DONT_CACHE state.&lt;/p&gt;
&lt;p&gt;This is not only a functional bug. Properly timed, a get_acl() from this
fuse filesystem can return a stale cached value, as was observed in tests,
because set_acl() does not invalidate the unintentional acl cache.&lt;/p&gt;
&lt;p&gt;We could fix this in fuse, but it actually makes no sense for the vfs
helper forget_cached_acl() to invalidate the ACL_DONT_CACHE state, so
let it not do that to fix fuse and future users of ACL_DONT_CACHE.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-68149</guid>
    </item>
  </channel>
</rss>
