<?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 16:40:26 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-89660 — NFSD: Prevent client use-after-free during admin state revocation</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-89660</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 admin state revocation&lt;/p&gt;
&lt;p&gt;A stateid holds only a bare pointer to its nfs4_client; a stateid
reference does not pin it.  The client survives only because
__destroy_client() drains its stateids before free_client() runs.&lt;/p&gt;
&lt;p&gt;nfsd4_revoke_states() drops nn-&amp;gt;client_lock across revoke_one_stid(),
which dereferences the client to revoke a stateid and read
clp-&amp;gt;cl_minorversion.  A teardown racing the dropped lock can free
the client first.&lt;/p&gt;
&lt;p&gt;Pinning cl_rpc_users under client_lock blocks the DESTROY_CLIENTID and
EXCHANGE_ID teardown, which refuses while cl_rpc_users is non-zero.
force_expire_client() ignores it: once its wait for cl_rpc_users to
reach zero has passed, a later pin goes unnoticed.&lt;/p&gt;
&lt;p&gt;Under client_lock, skip a client whose cl_time is already zero --
force_expire_client() clears it there before waiting -- otherwise pin
cl_rpc_users before dropping the lock.  The walk then either sees the
expiry and skips, or pins in time for that wait to cover the revoke.&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 admin state revocation&lt;/p&gt;
&lt;p&gt;A stateid holds only a bare pointer to its nfs4_client; a stateid
reference does not pin it.  The client survives only because
__destroy_client() drains its stateids before free_client() runs.&lt;/p&gt;
&lt;p&gt;nfsd4_revoke_states() drops nn-&amp;gt;client_lock across revoke_one_stid(),
which dereferences the client to revoke a stateid and read
clp-&amp;gt;cl_minorversion.  A teardown racing the dropped lock can free
the client first.&lt;/p&gt;
&lt;p&gt;Pinning cl_rpc_users under client_lock blocks the DESTROY_CLIENTID and
EXCHANGE_ID teardown, which refuses while cl_rpc_users is non-zero.
force_expire_client() ignores it: once its wait for cl_rpc_users to
reach zero has passed, a later pin goes unnoticed.&lt;/p&gt;
&lt;p&gt;Under client_lock, skip a client whose cl_time is already zero --
force_expire_client() clears it there before waiting -- otherwise pin
cl_rpc_users before dropping the lock.  The walk then either sees the
expiry and skips, or pins in time for that wait to cover the revoke.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-89660</guid>
    </item>
  </channel>
</rss>
