<?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>Thu, 05 Nov 2026 00:36:37 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-98843</title>
      <link>https://db.gcve.eu/vuln/fkie_cve-2026-98843</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;netfs: zero gaps in read-gaps folio to avoid writing back stale data&lt;/p&gt;
&lt;p&gt;netfs_read_gaps() leaves gaps around a streaming write&amp;#39;s dirty region
unread on the server side, so a short/EOF response there left stale
folio content that later got written back.&lt;/p&gt;
&lt;p&gt;Zero it after the read completes, not before: netfs_wait_for_read()
returns rreq-&amp;gt;transferred once ret &amp;gt;= 0, so build an iterator over the
same bvec array the read used, advance past ret, and zero the rest.
The dirty region already maps to sink pages in that array rather than
the real folio, so this can&amp;#39;t touch it, and only the actual shortfall
gets zeroed instead of the whole gap upfront.&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;netfs: zero gaps in read-gaps folio to avoid writing back stale data&lt;/p&gt;
&lt;p&gt;netfs_read_gaps() leaves gaps around a streaming write&amp;#39;s dirty region
unread on the server side, so a short/EOF response there left stale
folio content that later got written back.&lt;/p&gt;
&lt;p&gt;Zero it after the read completes, not before: netfs_wait_for_read()
returns rreq-&amp;gt;transferred once ret &amp;gt;= 0, so build an iterator over the
same bvec array the read used, advance past ret, and zero the rest.
The dirty region already maps to sink pages in that array rather than
the real folio, so this can&amp;#39;t touch it, and only the actual shortfall
gets zeroed instead of the whole gap upfront.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/fkie_cve-2026-98843</guid>
    </item>
    <item>
      <title>GHSA-3x6r-43qp-fxh7</title>
      <link>https://db.gcve.eu/vuln/ghsa-3x6r-43qp-fxh7</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;netfs: zero gaps in read-gaps folio to avoid writing back stale data&lt;/p&gt;
&lt;p&gt;netfs_read_gaps() leaves gaps around a streaming write&amp;#39;s dirty region
unread on the server side, so a short/EOF response there left stale
folio content that later got written back.&lt;/p&gt;
&lt;p&gt;Zero it after the read completes, not before: netfs_wait_for_read()
returns rreq-&amp;gt;transferred once ret &amp;gt;= 0, so build an iterator over the
same bvec array the read used, advance past ret, and zero the rest.
The dirty region already maps to sink pages in that array rather than
the real folio, so this can&amp;#39;t touch it, and only the actual shortfall
gets zeroed instead of the whole gap upfront.&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;netfs: zero gaps in read-gaps folio to avoid writing back stale data&lt;/p&gt;
&lt;p&gt;netfs_read_gaps() leaves gaps around a streaming write&amp;#39;s dirty region
unread on the server side, so a short/EOF response there left stale
folio content that later got written back.&lt;/p&gt;
&lt;p&gt;Zero it after the read completes, not before: netfs_wait_for_read()
returns rreq-&amp;gt;transferred once ret &amp;gt;= 0, so build an iterator over the
same bvec array the read used, advance past ret, and zero the rest.
The dirty region already maps to sink pages in that array rather than
the real folio, so this can&amp;#39;t touch it, and only the actual shortfall
gets zeroed instead of the whole gap upfront.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ghsa-3x6r-43qp-fxh7</guid>
    </item>
    <item>
      <title>msrc_CVE-2026-98843 — netfs: zero gaps in read-gaps folio to avoid writing back stale data</title>
      <link>https://db.gcve.eu/vuln/msrc_cve-2026-98843</link>
      <description>msrc_CVE-2026-98843</description>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/msrc_cve-2026-98843</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-98843</title>
      <link>https://db.gcve.eu/vuln/ubuntu-cve-2026-98843</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3, Ubuntu:18.04:LTS: linux-gke-4.15, Ubuntu:18.04:LTS: linux-gke-5.4 and 120 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: netfs: zero gaps in read-gaps folio to avoid writing back stale data netfs_read_gaps() leaves gaps around a streaming write&amp;#39;s dirty region unread on the server side, so a short/EOF response there left stale folio content that later got written back. Zero it after the read completes, not before: netfs_wait_for_read() returns rreq-&amp;gt;transferred once ret &amp;gt;= 0, so build an iterator over the same bvec array the read used, advance past ret, and zero the rest. The dirty region already maps to sink pages in that array rather than the real folio, so this can&amp;#39;t touch it, and only the actual shortfall gets zeroed instead of the whole gap upfront.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3, Ubuntu:18.04:LTS: linux-gke-4.15, Ubuntu:18.04:LTS: linux-gke-5.4 and 120 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: netfs: zero gaps in read-gaps folio to avoid writing back stale data netfs_read_gaps() leaves gaps around a streaming write&amp;#39;s dirty region unread on the server side, so a short/EOF response there left stale folio content that later got written back. Zero it after the read completes, not before: netfs_wait_for_read() returns rreq-&amp;gt;transferred once ret &amp;gt;= 0, so build an iterator over the same bvec array the read used, advance past ret, and zero the rest. The dirty region already maps to sink pages in that array rather than the real folio, so this can&amp;#39;t touch it, and only the actual shortfall gets zeroed instead of the whole gap upfront.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ubuntu-cve-2026-98843</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-4019 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://db.gcve.eu/vuln/wid-sec-w-2026-4019</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-4019</guid>
    </item>
  </channel>
</rss>
