<?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 05:26:12 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-98126 — smb/client: validate new EOF for zero range</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-98126</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;smb/client: validate new EOF for zero range&lt;/p&gt;
&lt;p&gt;When FALLOC_FL_ZERO_RANGE is used without FALLOC_FL_KEEP_SIZE,
smb3_zero_range() may extend EOF without checking RLIMIT_FSIZE, allowing
the file to grow beyond the caller&amp;#39;s file-size limit.&lt;/p&gt;
&lt;p&gt;Fix this by calling inode_newsize_ok() before sending the zero-range
request when the operation would extend EOF.&lt;/p&gt;
&lt;p&gt;Reproducer, using a file on a CIFS mount:&lt;/p&gt;
&lt;p&gt;bash -c &amp;#39;
	        FILE=/mnt/cifs/repro&lt;/p&gt;
&lt;p&gt;trap &amp;#34;&amp;#34; SIGXFSZ
	        ulimit -f 3072&lt;/p&gt;
&lt;p&gt;truncate -s 2M &amp;#34;$FILE&amp;#34;
	        fallocate --zero-range -o 0 -l 4M &amp;#34;$FILE&amp;#34;
	        echo &amp;#34;fallocate rc=$?&amp;#34;
	        stat -c &amp;#34;file size=%s&amp;#34; &amp;#34;$FILE&amp;#34;
	&amp;#39;&lt;/p&gt;
&lt;p&gt;Before this change, the operation succeeds despite the 3 MiB limit:&lt;/p&gt;
&lt;p&gt;fallocate rc=0
	file size=4194304&lt;/p&gt;
&lt;p&gt;After this change, fallocate fails and leaves the file at 2 MiB.&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;smb/client: validate new EOF for zero range&lt;/p&gt;
&lt;p&gt;When FALLOC_FL_ZERO_RANGE is used without FALLOC_FL_KEEP_SIZE,
smb3_zero_range() may extend EOF without checking RLIMIT_FSIZE, allowing
the file to grow beyond the caller&amp;#39;s file-size limit.&lt;/p&gt;
&lt;p&gt;Fix this by calling inode_newsize_ok() before sending the zero-range
request when the operation would extend EOF.&lt;/p&gt;
&lt;p&gt;Reproducer, using a file on a CIFS mount:&lt;/p&gt;
&lt;p&gt;bash -c &amp;#39;
	        FILE=/mnt/cifs/repro&lt;/p&gt;
&lt;p&gt;trap &amp;#34;&amp;#34; SIGXFSZ
	        ulimit -f 3072&lt;/p&gt;
&lt;p&gt;truncate -s 2M &amp;#34;$FILE&amp;#34;
	        fallocate --zero-range -o 0 -l 4M &amp;#34;$FILE&amp;#34;
	        echo &amp;#34;fallocate rc=$?&amp;#34;
	        stat -c &amp;#34;file size=%s&amp;#34; &amp;#34;$FILE&amp;#34;
	&amp;#39;&lt;/p&gt;
&lt;p&gt;Before this change, the operation succeeds despite the 3 MiB limit:&lt;/p&gt;
&lt;p&gt;fallocate rc=0
	file size=4194304&lt;/p&gt;
&lt;p&gt;After this change, fallocate fails and leaves the file at 2 MiB.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-98126</guid>
    </item>
  </channel>
</rss>
