<?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 07:24:38 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-89678 — nfsd: fix partial-write detection in nfsd_direct_write</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-89678</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: fix partial-write detection in nfsd_direct_write&lt;/p&gt;
&lt;p&gt;nfsd_direct_write() walks a list of write segments and, after each
vfs_iocb_iter_write(), tries to detect a short write so the loop can
stop before placing the next segment at a wrong file offset:&lt;/p&gt;
&lt;p&gt;host_err = vfs_iocb_iter_write(file, kiocb, &amp;amp;segments[i].iter);
    if (host_err &amp;lt; 0)
            return host_err;
    *cnt += host_err;
    if (host_err &amp;lt; segments[i].iter.count)
            break;	/* partial write */&lt;/p&gt;
&lt;p&gt;vfs_iocb_iter_write() runs the iter through -&amp;gt;write_iter(), which
advances the iter by the number of bytes written. By the time the
check runs, segments[i].iter.count is the residual, not the original
request length:&lt;/p&gt;
&lt;p&gt;before write_iter: iter.count == original_len
    after  write_iter: iter.count == original_len - host_err&lt;/p&gt;
&lt;p&gt;The condition then reduces to host_err &amp;lt; original_len - host_err, so
the break fires only when less than half of the segment was written.
Any short write completing between 50% and 99% of the segment slips
through; the loop advances to the next segment with kiocb-&amp;gt;ki_pos
only bumped by the short amount, writing the next segment&amp;#39;s payload
at the wrong offset and over-reporting *cnt to the NFS client.&lt;/p&gt;
&lt;p&gt;Snapshot the segment&amp;#39;s byte count before the write and compare
host_err against that snapshot so any short write breaks the loop.&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: fix partial-write detection in nfsd_direct_write&lt;/p&gt;
&lt;p&gt;nfsd_direct_write() walks a list of write segments and, after each
vfs_iocb_iter_write(), tries to detect a short write so the loop can
stop before placing the next segment at a wrong file offset:&lt;/p&gt;
&lt;p&gt;host_err = vfs_iocb_iter_write(file, kiocb, &amp;amp;segments[i].iter);
    if (host_err &amp;lt; 0)
            return host_err;
    *cnt += host_err;
    if (host_err &amp;lt; segments[i].iter.count)
            break;	/* partial write */&lt;/p&gt;
&lt;p&gt;vfs_iocb_iter_write() runs the iter through -&amp;gt;write_iter(), which
advances the iter by the number of bytes written. By the time the
check runs, segments[i].iter.count is the residual, not the original
request length:&lt;/p&gt;
&lt;p&gt;before write_iter: iter.count == original_len
    after  write_iter: iter.count == original_len - host_err&lt;/p&gt;
&lt;p&gt;The condition then reduces to host_err &amp;lt; original_len - host_err, so
the break fires only when less than half of the segment was written.
Any short write completing between 50% and 99% of the segment slips
through; the loop advances to the next segment with kiocb-&amp;gt;ki_pos
only bumped by the short amount, writing the next segment&amp;#39;s payload
at the wrong offset and over-reporting *cnt to the NFS client.&lt;/p&gt;
&lt;p&gt;Snapshot the segment&amp;#39;s byte count before the write and compare
host_err against that snapshot so any short write breaks the loop.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-89678</guid>
    </item>
  </channel>
</rss>
