<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://vulnerability.circl.lu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-09-29T05:26:13.613905+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@circl.lu</email>
  </author>
  <link href="https://vulnerability.circl.lu" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/cve-2026-98126</id>
    <title>CVE-2026-98126 — smb/client: validate new EOF for zero range</title>
    <updated>2026-09-29T05:26:13.614767+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Linux</p>
<p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>smb/client: validate new EOF for zero range</p>
<p>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's file-size limit.</p>
<p>Fix this by calling inode_newsize_ok() before sending the zero-range
request when the operation would extend EOF.</p>
<p>Reproducer, using a file on a CIFS mount:</p>
<p>bash -c '
	        FILE=/mnt/cifs/repro</p>
<p>trap "" SIGXFSZ
	        ulimit -f 3072</p>
<p>truncate -s 2M "$FILE"
	        fallocate --zero-range -o 0 -l 4M "$FILE"
	        echo "fallocate rc=$?"
	        stat -c "file size=%s" "$FILE"
	'</p>
<p>Before this change, the operation succeeds despite the 3 MiB limit:</p>
<p>fallocate rc=0
	file size=4194304</p>
<p>After this change, fallocate fails and leaves the file at 2 MiB.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2026-98126"/>
  </entry>
</feed>
