<?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://cve.radiocsirt.org</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>Mon, 05 Oct 2026 12:17:03 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-89691 — nfsd: clear opcnt on compound arg release to prevent OOB read</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2026-89691</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: clear opcnt on compound arg release to prevent OOB read&lt;/p&gt;
&lt;p&gt;nfsd4_release_compoundargs() resets args-&amp;gt;ops to the inline iops[8]
array when the dynamically-allocated ops buffer is freed, but leaves
args-&amp;gt;opcnt at its original value (which can be up to 200 for NFSv4.1+
compounds).&lt;/p&gt;
&lt;p&gt;If rq_status_counter is stuck at an odd value (which can happen when
nfsd_dispatch() hits an error path after setting it odd), the RPC
status dumpit handler reads min(opcnt, 16) entries from args-&amp;gt;ops[].
Since iops only has 8 elements and is the last field in struct
nfsd4_compoundargs, reading indices 8-15 accesses adjacent slab memory
and leaks it to userspace via netlink.&lt;/p&gt;
&lt;p&gt;Zero opcnt unconditionally in nfsd4_release_compoundargs() so stale
compound metadata is never exposed through the status interface.&lt;/p&gt;
&lt;p&gt;[ cel: Remove the kvfree_rcu_mightsleep() sleep from the exposure window ]&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: clear opcnt on compound arg release to prevent OOB read&lt;/p&gt;
&lt;p&gt;nfsd4_release_compoundargs() resets args-&amp;gt;ops to the inline iops[8]
array when the dynamically-allocated ops buffer is freed, but leaves
args-&amp;gt;opcnt at its original value (which can be up to 200 for NFSv4.1+
compounds).&lt;/p&gt;
&lt;p&gt;If rq_status_counter is stuck at an odd value (which can happen when
nfsd_dispatch() hits an error path after setting it odd), the RPC
status dumpit handler reads min(opcnt, 16) entries from args-&amp;gt;ops[].
Since iops only has 8 elements and is the last field in struct
nfsd4_compoundargs, reading indices 8-15 accesses adjacent slab memory
and leaks it to userspace via netlink.&lt;/p&gt;
&lt;p&gt;Zero opcnt unconditionally in nfsd4_release_compoundargs() so stale
compound metadata is never exposed through the status interface.&lt;/p&gt;
&lt;p&gt;[ cel: Remove the kvfree_rcu_mightsleep() sleep from the exposure window ]&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2026-89691</guid>
    </item>
  </channel>
</rss>
