<?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:29:51.724136+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-89640</id>
    <title>CVE-2026-89640 — cifs: fix loff_t underflow in cifs_remap_file_range() when len == 0</title>
    <updated>2026-09-29T05:29:51.726366+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>cifs: fix loff_t underflow in cifs_remap_file_range() when len == 0</p>
<p>With len == 0 (clone to EOF), the effective length is computed as:</p>
<p>len = src_inode-&gt;i_size - off;</p>
<p>If off &gt; i_size, this is a negative loff_t, corrupting the ByteCount
in the FSCTL_DUPLICATE_EXTENTS_TO_FILE request and inverting the range
in filemap_write_and_wait_range().  The existing off &gt;= i_size check
fires only after the ioctl has already been sent.</p>
<p>Snapshot i_size_read() once for both the bounds check and the length
calculation, eliminating the TOCTOU and 32-bit torn-read risk.  Reject
off &gt; src_size with -EINVAL.  Treat off == src_size as a no-op,
consistent with __generic_remap_file_range_prep().</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2026-89640"/>
  </entry>
</feed>
