<?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>Tue, 29 Sep 2026 07:32:02 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-90038 — NFSD: Prevent client use-after-free during export state revocation</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-90038</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: Prevent client use-after-free during export state revocation&lt;/p&gt;
&lt;p&gt;nfsd4_revoke_export_states() has the same use-after-free as
nfsd4_revoke_states(): it drops nn-&amp;gt;client_lock across
revoke_one_stid() and the following read of clp-&amp;gt;cl_minorversion, but
the stateid reference it holds does not pin the client.  A teardown
racing the dropped lock can free the client while revoke_one_stid()
still dereferences it.&lt;/p&gt;
&lt;p&gt;exportfs -u drives this path through NFSD_CMD_UNLOCK_EXPORT, so an
administrator removing an export can race a client expiry.&lt;/p&gt;
&lt;p&gt;Skip a client that is already expiring and otherwise pin it with
cl_rpc_users under client_lock before dropping the lock, matching
nfsd4_revoke_states().&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: Prevent client use-after-free during export state revocation&lt;/p&gt;
&lt;p&gt;nfsd4_revoke_export_states() has the same use-after-free as
nfsd4_revoke_states(): it drops nn-&amp;gt;client_lock across
revoke_one_stid() and the following read of clp-&amp;gt;cl_minorversion, but
the stateid reference it holds does not pin the client.  A teardown
racing the dropped lock can free the client while revoke_one_stid()
still dereferences it.&lt;/p&gt;
&lt;p&gt;exportfs -u drives this path through NFSD_CMD_UNLOCK_EXPORT, so an
administrator removing an export can race a client expiry.&lt;/p&gt;
&lt;p&gt;Skip a client that is already expiring and otherwise pin it with
cl_rpc_users under client_lock before dropping the lock, matching
nfsd4_revoke_states().&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-90038</guid>
    </item>
  </channel>
</rss>
