<?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:23:15 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-99366 — nfsd: don't modify a session slot when replaying its cached reply</title>
      <link>https://db.gcve.eu/vuln/cve-2026-99366</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: don&amp;#39;t modify a session slot when replaying its cached reply&lt;/p&gt;
&lt;p&gt;nfsd4_sequence() claims a session slot by setting NFSD4_SLOT_INUSE
under nn-&amp;gt;client_lock. A reply served from the slot&amp;#39;s reply cache does
not claim it, and that distinction lived only in cstate-&amp;gt;status, which
nfsd4_sequence() set to nfserr_replay_cache. Commit cc028a10a48c
(&amp;#34;NFSD: Hoist status code encoding into XDR encoder functions&amp;#34;) moved
nfsd4_proc_compound()&amp;#39;s cstate-&amp;gt;status assignment below the out:
label, and the replay path&amp;#39;s goto out was the one path that relied on
skipping it. The test in nfsd4_sequence_done() therefore no longer
identifies a replay, and every replay now stores its reply and clears
NFSD4_SLOT_INUSE as though it owned the slot.&lt;/p&gt;
&lt;p&gt;NFSD4_SLOT_INUSE is the interlock: check_slot_seqid() rejects every
sequence id for a slot that is in use, before replay_matches_cache()
runs. A replay never sets it, so two replays can be in flight on the
same slot at once. One can read slot-&amp;gt;sl_cred under nn-&amp;gt;client_lock
while the other&amp;#39;s completion frees and rebuilds it from the XDR
encoder without that lock. Two completions can also collide with each
other and release the same group_info twice. free_svc_cred() leaves
cr_uid, cr_gid and cr_flavor intact, so the reader passes every
earlier test in same_creds() and dereferences a NULL cr_group_info.
From a 6.12.91 production server:&lt;/p&gt;
&lt;p&gt;BUG: kernel NULL pointer dereference, address: 00000000…&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: don&amp;#39;t modify a session slot when replaying its cached reply&lt;/p&gt;
&lt;p&gt;nfsd4_sequence() claims a session slot by setting NFSD4_SLOT_INUSE
under nn-&amp;gt;client_lock. A reply served from the slot&amp;#39;s reply cache does
not claim it, and that distinction lived only in cstate-&amp;gt;status, which
nfsd4_sequence() set to nfserr_replay_cache. Commit cc028a10a48c
(&amp;#34;NFSD: Hoist status code encoding into XDR encoder functions&amp;#34;) moved
nfsd4_proc_compound()&amp;#39;s cstate-&amp;gt;status assignment below the out:
label, and the replay path&amp;#39;s goto out was the one path that relied on
skipping it. The test in nfsd4_sequence_done() therefore no longer
identifies a replay, and every replay now stores its reply and clears
NFSD4_SLOT_INUSE as though it owned the slot.&lt;/p&gt;
&lt;p&gt;NFSD4_SLOT_INUSE is the interlock: check_slot_seqid() rejects every
sequence id for a slot that is in use, before replay_matches_cache()
runs. A replay never sets it, so two replays can be in flight on the
same slot at once. One can read slot-&amp;gt;sl_cred under nn-&amp;gt;client_lock
while the other&amp;#39;s completion frees and rebuilds it from the XDR
encoder without that lock. Two completions can also collide with each
other and release the same group_info twice. free_svc_cred() leaves
cr_uid, cr_gid and cr_flavor intact, so the reader passes every
earlier test in same_creds() and dereferences a NULL cr_group_info.
From a 6.12.91 production server:&lt;/p&gt;
&lt;p&gt;BUG: kernel NULL pointer dereference, address: 00000000…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/cve-2026-99366</guid>
    </item>
  </channel>
</rss>
