<?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 20:53:23 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-99789 — block: restore the iterator when rejecting a misaligned bio</title>
      <link>https://db.gcve.eu/vuln/cve-2026-99789</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;block: restore the iterator when rejecting a misaligned bio&lt;/p&gt;
&lt;p&gt;bio_iov_iter_get_pages() can extract some iovecs before encountering a
misaligned one.  It releases the pages and rejects the entire bio, but
leaves the supplied iterator advanced.&lt;/p&gt;
&lt;p&gt;An iomap direct-I/O caller may subsequently reexpand the iterator&amp;#39;s
byte count and fall back to buffered I/O.  The reexpanded count then
includes bytes before the iterator&amp;#39;s current segment, potentially
causing iterate_iovec() to read beyond the imported iovec array.&lt;/p&gt;
&lt;p&gt;In a reproducer using an initial empty iovec followed by 10-byte and
1015-byte segments, writev() returned 1015 instead of 1025 and KASAN
reported an 8-byte read beyond the nine-element iovec allocation.
Saving and restoring the iterator on the rejected-bio path makes
writev() return 1025 and eliminates the KASAN report.&lt;/p&gt;
&lt;p&gt;Restore the entire iterator rather than reverting a byte count:
advancing past an empty segment changes its position without consuming
any bytes.&lt;/p&gt;
&lt;p&gt;Leave successful and partially accepted bio paths unchanged.&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;block: restore the iterator when rejecting a misaligned bio&lt;/p&gt;
&lt;p&gt;bio_iov_iter_get_pages() can extract some iovecs before encountering a
misaligned one.  It releases the pages and rejects the entire bio, but
leaves the supplied iterator advanced.&lt;/p&gt;
&lt;p&gt;An iomap direct-I/O caller may subsequently reexpand the iterator&amp;#39;s
byte count and fall back to buffered I/O.  The reexpanded count then
includes bytes before the iterator&amp;#39;s current segment, potentially
causing iterate_iovec() to read beyond the imported iovec array.&lt;/p&gt;
&lt;p&gt;In a reproducer using an initial empty iovec followed by 10-byte and
1015-byte segments, writev() returned 1015 instead of 1025 and KASAN
reported an 8-byte read beyond the nine-element iovec allocation.
Saving and restoring the iterator on the rejected-bio path makes
writev() return 1025 and eliminates the KASAN report.&lt;/p&gt;
&lt;p&gt;Restore the entire iterator rather than reverting a byte count:
advancing past an empty segment changes its position without consuming
any bytes.&lt;/p&gt;
&lt;p&gt;Leave successful and partially accepted bio paths unchanged.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/cve-2026-99789</guid>
    </item>
  </channel>
</rss>
