<?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://db.gcve.eu</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>Fri, 20 Nov 2026 21:05:51 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-99373</title>
      <link>https://db.gcve.eu/vuln/fkie_cve-2026-99373</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;NFS/localio: detect a short read or write before the iterator has moved&lt;/p&gt;
&lt;p&gt;nfs_local_call_read() and nfs_local_call_write() issue a misaligned
DIO as up to three segments and must stop at the first short one, or
the next segment lands at the wrong file offset.  They test for that
by comparing the bytes transferred against iov_iter_count() of the
segment, read after read_iter() or write_iter() has advanced the
iterator, when the count is the residual rather than the request:&lt;/p&gt;
&lt;p&gt;before the call:  count == expected
    after the call:   count == expected - status&lt;/p&gt;
&lt;p&gt;The test is therefore status &amp;lt; expected - status, and it fires only
when less than half of the segment was transferred.  A short I/O that
covers between 50% and 99% of a segment slips through: the loop moves
on with ki_pos advanced by the short amount, the next segment is
issued at the wrong offset, and the header&amp;#39;s byte count is
over-reported to the caller.  A write that slips through also never
sets NFS_CONTEXT_WRITE_SYNC, which is what makes the writes that
follow a short one synchronous.&lt;/p&gt;
&lt;p&gt;Take the segment&amp;#39;s count before issuing it and compare against that.&lt;/p&gt;
&lt;p&gt;This is the same defect that commit 250ec14932d5 (&amp;#34;nfsd: fix
partial-write detection in nfsd_direct_write&amp;#34;) fixed in NFSD&amp;#39;s version
of this loop.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;NFS/localio: detect a short read or write before the iterator has moved&lt;/p&gt;
&lt;p&gt;nfs_local_call_read() and nfs_local_call_write() issue a misaligned
DIO as up to three segments and must stop at the first short one, or
the next segment lands at the wrong file offset.  They test for that
by comparing the bytes transferred against iov_iter_count() of the
segment, read after read_iter() or write_iter() has advanced the
iterator, when the count is the residual rather than the request:&lt;/p&gt;
&lt;p&gt;before the call:  count == expected
    after the call:   count == expected - status&lt;/p&gt;
&lt;p&gt;The test is therefore status &amp;lt; expected - status, and it fires only
when less than half of the segment was transferred.  A short I/O that
covers between 50% and 99% of a segment slips through: the loop moves
on with ki_pos advanced by the short amount, the next segment is
issued at the wrong offset, and the header&amp;#39;s byte count is
over-reported to the caller.  A write that slips through also never
sets NFS_CONTEXT_WRITE_SYNC, which is what makes the writes that
follow a short one synchronous.&lt;/p&gt;
&lt;p&gt;Take the segment&amp;#39;s count before issuing it and compare against that.&lt;/p&gt;
&lt;p&gt;This is the same defect that commit 250ec14932d5 (&amp;#34;nfsd: fix
partial-write detection in nfsd_direct_write&amp;#34;) fixed in NFSD&amp;#39;s version
of this loop.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/fkie_cve-2026-99373</guid>
    </item>
    <item>
      <title>GHSA-wr9g-2r2q-j77f</title>
      <link>https://db.gcve.eu/vuln/ghsa-wr9g-2r2q-j77f</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;NFS/localio: detect a short read or write before the iterator has moved&lt;/p&gt;
&lt;p&gt;nfs_local_call_read() and nfs_local_call_write() issue a misaligned
DIO as up to three segments and must stop at the first short one, or
the next segment lands at the wrong file offset.  They test for that
by comparing the bytes transferred against iov_iter_count() of the
segment, read after read_iter() or write_iter() has advanced the
iterator, when the count is the residual rather than the request:&lt;/p&gt;
&lt;p&gt;before the call:  count == expected
    after the call:   count == expected - status&lt;/p&gt;
&lt;p&gt;The test is therefore status &amp;lt; expected - status, and it fires only
when less than half of the segment was transferred.  A short I/O that
covers between 50% and 99% of a segment slips through: the loop moves
on with ki_pos advanced by the short amount, the next segment is
issued at the wrong offset, and the header&amp;#39;s byte count is
over-reported to the caller.  A write that slips through also never
sets NFS_CONTEXT_WRITE_SYNC, which is what makes the writes that
follow a short one synchronous.&lt;/p&gt;
&lt;p&gt;Take the segment&amp;#39;s count before issuing it and compare against that.&lt;/p&gt;
&lt;p&gt;This is the same defect that commit 250ec14932d5 (&amp;#34;nfsd: fix
partial-write detection in nfsd_direct_write&amp;#34;) fixed in NFSD&amp;#39;s version
of this loop.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;NFS/localio: detect a short read or write before the iterator has moved&lt;/p&gt;
&lt;p&gt;nfs_local_call_read() and nfs_local_call_write() issue a misaligned
DIO as up to three segments and must stop at the first short one, or
the next segment lands at the wrong file offset.  They test for that
by comparing the bytes transferred against iov_iter_count() of the
segment, read after read_iter() or write_iter() has advanced the
iterator, when the count is the residual rather than the request:&lt;/p&gt;
&lt;p&gt;before the call:  count == expected
    after the call:   count == expected - status&lt;/p&gt;
&lt;p&gt;The test is therefore status &amp;lt; expected - status, and it fires only
when less than half of the segment was transferred.  A short I/O that
covers between 50% and 99% of a segment slips through: the loop moves
on with ki_pos advanced by the short amount, the next segment is
issued at the wrong offset, and the header&amp;#39;s byte count is
over-reported to the caller.  A write that slips through also never
sets NFS_CONTEXT_WRITE_SYNC, which is what makes the writes that
follow a short one synchronous.&lt;/p&gt;
&lt;p&gt;Take the segment&amp;#39;s count before issuing it and compare against that.&lt;/p&gt;
&lt;p&gt;This is the same defect that commit 250ec14932d5 (&amp;#34;nfsd: fix
partial-write detection in nfsd_direct_write&amp;#34;) fixed in NFSD&amp;#39;s version
of this loop.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ghsa-wr9g-2r2q-j77f</guid>
    </item>
    <item>
      <title>msrc_CVE-2026-99373 — NFS/localio: detect a short read or write before the iterator has moved</title>
      <link>https://db.gcve.eu/vuln/msrc_cve-2026-99373</link>
      <description>msrc_CVE-2026-99373</description>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/msrc_cve-2026-99373</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-4695 — Linux Kernel: Mehrere Schwachstellen ermöglichen nicht spezifizierten Angriff</title>
      <link>https://db.gcve.eu/vuln/wid-sec-w-2026-4695</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen, möglicherweise einen Denial-of-Service-Angriff auszulösen, Daten zu manipulieren oder offenzulegen oder Sicherheitsmaßnahmen zu umgehen&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen, möglicherweise einen Denial-of-Service-Angriff auszulösen, Daten zu manipulieren oder offenzulegen oder Sicherheitsmaßnahmen zu umgehen&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/wid-sec-w-2026-4695</guid>
    </item>
  </channel>
</rss>
