<?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>Wed, 07 Oct 2026 10:53:44 +0000</lastBuildDate>
    <item>
      <title>CVE-2023-53083 — nfsd: don't replace page in rq_pages if it's a continuation of last page</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2023-53083</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 replace page in rq_pages if it&amp;#39;s a continuation of last page&lt;/p&gt;
&lt;p&gt;The splice read calls nfsd_splice_actor to put the pages containing file
data into the svc_rqst-&amp;gt;rq_pages array. It&amp;#39;s possible however to get a
splice result that only has a partial page at the end, if (e.g.) the
filesystem hands back a short read that doesn&amp;#39;t cover the whole page.&lt;/p&gt;
&lt;p&gt;nfsd_splice_actor will plop the partial page into its rq_pages array and
return. Then later, when nfsd_splice_actor is called again, the
remainder of the page may end up being filled out. At this point,
nfsd_splice_actor will put the page into the array _again_ corrupting
the reply. If this is done enough times, rq_next_page will overrun the
array and corrupt the trailing fields -- the rq_respages and
rq_next_page pointers themselves.&lt;/p&gt;
&lt;p&gt;If we&amp;#39;ve already added the page to the array in the last pass, don&amp;#39;t add
it to the array a second time when dealing with a splice continuation.
This was originally handled properly in nfsd_splice_actor, but commit
91e23b1c3982 (&amp;#34;NFSD: Clean up nfsd_splice_actor()&amp;#34;) removed the check
for it.&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 replace page in rq_pages if it&amp;#39;s a continuation of last page&lt;/p&gt;
&lt;p&gt;The splice read calls nfsd_splice_actor to put the pages containing file
data into the svc_rqst-&amp;gt;rq_pages array. It&amp;#39;s possible however to get a
splice result that only has a partial page at the end, if (e.g.) the
filesystem hands back a short read that doesn&amp;#39;t cover the whole page.&lt;/p&gt;
&lt;p&gt;nfsd_splice_actor will plop the partial page into its rq_pages array and
return. Then later, when nfsd_splice_actor is called again, the
remainder of the page may end up being filled out. At this point,
nfsd_splice_actor will put the page into the array _again_ corrupting
the reply. If this is done enough times, rq_next_page will overrun the
array and corrupt the trailing fields -- the rq_respages and
rq_next_page pointers themselves.&lt;/p&gt;
&lt;p&gt;If we&amp;#39;ve already added the page to the array in the last pass, don&amp;#39;t add
it to the array a second time when dealing with a splice continuation.
This was originally handled properly in nfsd_splice_actor, but commit
91e23b1c3982 (&amp;#34;NFSD: Clean up nfsd_splice_actor()&amp;#34;) removed the check
for it.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2023-53083</guid>
    </item>
  </channel>
</rss>
