<?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>Sun, 04 Oct 2026 05:07:19 +0000</lastBuildDate>
    <item>
      <title>CVE-2024-27036 — cifs: Fix writeback data corruption</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2024-27036</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;cifs: Fix writeback data corruption&lt;/p&gt;
&lt;p&gt;cifs writeback doesn&amp;#39;t correctly handle the case where
cifs_extend_writeback() hits a point where it is considering an additional
folio, but this would overrun the wsize - at which point it drops out of
the xarray scanning loop and calls xas_pause().  The problem is that
xas_pause() advances the loop counter - thereby skipping that page.&lt;/p&gt;
&lt;p&gt;What needs to happen is for xas_reset() to be called any time we decide we
don&amp;#39;t want to process the page we&amp;#39;re looking at, but rather send the
request we are building and start a new one.&lt;/p&gt;
&lt;p&gt;Fix this by copying and adapting the netfslib writepages code as a
temporary measure, with cifs writeback intending to be offloaded to
netfslib in the near future.&lt;/p&gt;
&lt;p&gt;This also fixes the issue with the use of filemap_get_folios_tag() causing
retry of a bunch of pages which the extender already dealt with.&lt;/p&gt;
&lt;p&gt;This can be tested by creating, say, a 64K file somewhere not on cifs
(otherwise copy-offload may get underfoot), mounting a cifs share with a
wsize of 64000, copying the file to it and then comparing the original file
and the copy:&lt;/p&gt;
&lt;p&gt;dd if=/dev/urandom of=/tmp/64K bs=64k count=1
        mount //192.168.6.1/test /mnt -o user=...,pass=...,wsize=64000
        cp /tmp/64K /mnt/64K
        cmp /tmp/64K /mnt/64K&lt;/p&gt;
&lt;p&gt;Without the fix, the cmp fails at position 64000 (or shortly thereafter).&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;cifs: Fix writeback data corruption&lt;/p&gt;
&lt;p&gt;cifs writeback doesn&amp;#39;t correctly handle the case where
cifs_extend_writeback() hits a point where it is considering an additional
folio, but this would overrun the wsize - at which point it drops out of
the xarray scanning loop and calls xas_pause().  The problem is that
xas_pause() advances the loop counter - thereby skipping that page.&lt;/p&gt;
&lt;p&gt;What needs to happen is for xas_reset() to be called any time we decide we
don&amp;#39;t want to process the page we&amp;#39;re looking at, but rather send the
request we are building and start a new one.&lt;/p&gt;
&lt;p&gt;Fix this by copying and adapting the netfslib writepages code as a
temporary measure, with cifs writeback intending to be offloaded to
netfslib in the near future.&lt;/p&gt;
&lt;p&gt;This also fixes the issue with the use of filemap_get_folios_tag() causing
retry of a bunch of pages which the extender already dealt with.&lt;/p&gt;
&lt;p&gt;This can be tested by creating, say, a 64K file somewhere not on cifs
(otherwise copy-offload may get underfoot), mounting a cifs share with a
wsize of 64000, copying the file to it and then comparing the original file
and the copy:&lt;/p&gt;
&lt;p&gt;dd if=/dev/urandom of=/tmp/64K bs=64k count=1
        mount //192.168.6.1/test /mnt -o user=...,pass=...,wsize=64000
        cp /tmp/64K /mnt/64K
        cmp /tmp/64K /mnt/64K&lt;/p&gt;
&lt;p&gt;Without the fix, the cmp fails at position 64000 (or shortly thereafter).&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2024-27036</guid>
    </item>
  </channel>
</rss>
