<?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:00:37 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-89710 — NFSv4.1: fix layout segment leak on the pnfs_layout_process() forget path</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-89710</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;NFSv4.1: fix layout segment leak on the pnfs_layout_process() forget path&lt;/p&gt;
&lt;p&gt;When the server returns a new layout stateid while a valid one is still
held, pnfs_layout_process() calls pnfs_mark_matching_lsegs_return() on
the on-stack free_me list and jumps to out_forget. Segments whose
reference count drops to zero are unlinked from lo-&amp;gt;plh_segs and moved
to free_me by mark_lseg_invalid(); for an idle cached segment the layout
header holds the only reference, so this happens on the first decrement.&lt;/p&gt;
&lt;p&gt;out_forget never drains free_me -- only the success path calls
pnfs_free_lseg_list().&lt;/p&gt;
&lt;p&gt;Commit 814b84971388 (&amp;#34;pNFS/NFSv4: Fix a layout segment leak in
pnfs_layout_process()&amp;#34;) added the drain; commit 08bd8dbe8882
(&amp;#34;pNFS/NFSv4: Try to return invalid layout in pnfs_layout_process()&amp;#34;)
removed it while switching the destination to lo-&amp;gt;plh_return_segs, which
is drained elsewhere. Commit fb700ef02676 (&amp;#34;NFSv4.1: Simplify layout
return in pnfs_layout_process()&amp;#34;) switched the destination back to
free_me without restoring the drain.&lt;/p&gt;
&lt;p&gt;Restore the pnfs_free_lseg_list() call.&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;NFSv4.1: fix layout segment leak on the pnfs_layout_process() forget path&lt;/p&gt;
&lt;p&gt;When the server returns a new layout stateid while a valid one is still
held, pnfs_layout_process() calls pnfs_mark_matching_lsegs_return() on
the on-stack free_me list and jumps to out_forget. Segments whose
reference count drops to zero are unlinked from lo-&amp;gt;plh_segs and moved
to free_me by mark_lseg_invalid(); for an idle cached segment the layout
header holds the only reference, so this happens on the first decrement.&lt;/p&gt;
&lt;p&gt;out_forget never drains free_me -- only the success path calls
pnfs_free_lseg_list().&lt;/p&gt;
&lt;p&gt;Commit 814b84971388 (&amp;#34;pNFS/NFSv4: Fix a layout segment leak in
pnfs_layout_process()&amp;#34;) added the drain; commit 08bd8dbe8882
(&amp;#34;pNFS/NFSv4: Try to return invalid layout in pnfs_layout_process()&amp;#34;)
removed it while switching the destination to lo-&amp;gt;plh_return_segs, which
is drained elsewhere. Commit fb700ef02676 (&amp;#34;NFSv4.1: Simplify layout
return in pnfs_layout_process()&amp;#34;) switched the destination back to
free_me without restoring the drain.&lt;/p&gt;
&lt;p&gt;Restore the pnfs_free_lseg_list() call.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-89710</guid>
    </item>
  </channel>
</rss>
