<?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:43:27 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-53395 — nfsd: fix dead ACL conflict guard in nfsd4_create</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-53395</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;nfsd: fix dead ACL conflict guard in nfsd4_create&lt;/p&gt;
&lt;p&gt;nfsd4_create() steals create-&amp;gt;cr_dpacl/cr_pacl into the local
nfsd_attrs via the designated initializer, then immediately sets the
source pointers to NULL. The subsequent conflict guard tests the
already-nilled source fields, making it permanently dead code:&lt;/p&gt;
&lt;p&gt;if (create-&amp;gt;cr_acl) {
        if (create-&amp;gt;cr_dpacl || create-&amp;gt;cr_pacl)  /* always false */&lt;/p&gt;
&lt;p&gt;When a client encodes both FATTR4_WORD0_ACL and
FATTR4_WORD2_POSIX_{DEFAULT,ACCESS}_ACL in the same CREATE fattr
bitmap, nfsd4_acl_to_attr() overwrites attrs.na_pacl/na_dpacl without
releasing the originals, leaking two posix_acl slab objects per
request. Repeated requests cause unbounded slab exhaustion.&lt;/p&gt;
&lt;p&gt;Fix by checking attrs.na_dpacl/na_pacl (the stolen values) instead of
the nilled create-&amp;gt;cr_dpacl/cr_pacl, matching the correct pattern
already used in nfsd4_setattr().&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;nfsd: fix dead ACL conflict guard in nfsd4_create&lt;/p&gt;
&lt;p&gt;nfsd4_create() steals create-&amp;gt;cr_dpacl/cr_pacl into the local
nfsd_attrs via the designated initializer, then immediately sets the
source pointers to NULL. The subsequent conflict guard tests the
already-nilled source fields, making it permanently dead code:&lt;/p&gt;
&lt;p&gt;if (create-&amp;gt;cr_acl) {
        if (create-&amp;gt;cr_dpacl || create-&amp;gt;cr_pacl)  /* always false */&lt;/p&gt;
&lt;p&gt;When a client encodes both FATTR4_WORD0_ACL and
FATTR4_WORD2_POSIX_{DEFAULT,ACCESS}_ACL in the same CREATE fattr
bitmap, nfsd4_acl_to_attr() overwrites attrs.na_pacl/na_dpacl without
releasing the originals, leaking two posix_acl slab objects per
request. Repeated requests cause unbounded slab exhaustion.&lt;/p&gt;
&lt;p&gt;Fix by checking attrs.na_dpacl/na_pacl (the stolen values) instead of
the nilled create-&amp;gt;cr_dpacl/cr_pacl, matching the correct pattern
already used in nfsd4_setattr().&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-53395</guid>
    </item>
  </channel>
</rss>
