<?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 20:42:03 +0000</lastBuildDate>
    <item>
      <title>CVE-2025-40210 — Revert "NFSD: Remove the cap on number of operations per NFSv4 COMPOUND"</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2025-40210</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;Revert &amp;#34;NFSD: Remove the cap on number of operations per NFSv4 COMPOUND&amp;#34;&lt;/p&gt;
&lt;p&gt;I&amp;#39;ve found that pynfs COMP6 now leaves the connection or lease in a
strange state, which causes CLOSE9 to hang indefinitely. I&amp;#39;ve dug
into it a little, but I haven&amp;#39;t been able to root-cause it yet.
However, I bisected to commit 48aab1606fa8 (&amp;#34;NFSD: Remove the cap on
number of operations per NFSv4 COMPOUND&amp;#34;).&lt;/p&gt;
&lt;p&gt;Tianshuo Han also reports a potential vulnerability when decoding
an NFSv4 COMPOUND. An attacker can place an arbitrarily large op
count in the COMPOUND header, which results in:&lt;/p&gt;
&lt;p&gt;[   51.410584] nfsd: vmalloc error: size 1209533382144, exceeds total
pages, mode:0xdc0(GFP_KERNEL|__GFP_ZERO),
nodemask=(null),cpuset=/,mems_allowed=0&lt;/p&gt;
&lt;p&gt;when NFSD attempts to allocate the COMPOUND op array.&lt;/p&gt;
&lt;p&gt;Let&amp;#39;s restore the operation-per-COMPOUND limit, but increased to 200
for now.&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;Revert &amp;#34;NFSD: Remove the cap on number of operations per NFSv4 COMPOUND&amp;#34;&lt;/p&gt;
&lt;p&gt;I&amp;#39;ve found that pynfs COMP6 now leaves the connection or lease in a
strange state, which causes CLOSE9 to hang indefinitely. I&amp;#39;ve dug
into it a little, but I haven&amp;#39;t been able to root-cause it yet.
However, I bisected to commit 48aab1606fa8 (&amp;#34;NFSD: Remove the cap on
number of operations per NFSv4 COMPOUND&amp;#34;).&lt;/p&gt;
&lt;p&gt;Tianshuo Han also reports a potential vulnerability when decoding
an NFSv4 COMPOUND. An attacker can place an arbitrarily large op
count in the COMPOUND header, which results in:&lt;/p&gt;
&lt;p&gt;[   51.410584] nfsd: vmalloc error: size 1209533382144, exceeds total
pages, mode:0xdc0(GFP_KERNEL|__GFP_ZERO),
nodemask=(null),cpuset=/,mems_allowed=0&lt;/p&gt;
&lt;p&gt;when NFSD attempts to allocate the COMPOUND op array.&lt;/p&gt;
&lt;p&gt;Let&amp;#39;s restore the operation-per-COMPOUND limit, but increased to 200
for now.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2025-40210</guid>
    </item>
  </channel>
</rss>
