<?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>Mon, 28 Sep 2026 23:48:42 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-98125</title>
      <link>https://vulnerability.circl.lu/vuln/fkie_cve-2026-98125</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;smb/client: fix stale page cache in insert/collapse range&lt;/p&gt;
&lt;p&gt;smb3_insert_range() and smb3_collapse_range() use
truncate_pagecache_range() to invalidate the affected page cache.
However, if off or old_eof is not page-aligned, the boundary pages are
only partially zeroed and remain uptodate. As a result, the client may
return stale data after a successful insert/collapse range operation.&lt;/p&gt;
&lt;p&gt;For example, with 4K pages:&lt;/p&gt;
&lt;p&gt;page 0          page 1          page 2
    0------4K       4K------8K      8K------12K
       ^                                ^
    off=2K                       old_eof=10K&lt;/p&gt;
&lt;p&gt;Page 1 is removed from the page cache, while the boundary pages are
only partially zeroed. After COPYCHUNK moves the data on the server,
these cached pages may still return stale data.&lt;/p&gt;
&lt;p&gt;This can be reproduced on a CIFS mount:&lt;/p&gt;
&lt;p&gt;bash -c &amp;#39;
            FILE=/mnt/scratch/repro&lt;/p&gt;
&lt;p&gt;# Use a 6 KiB file so EOF is not page-aligned.
            dd if=/dev/urandom of=/tmp/src bs=1K count=6 status=none&lt;/p&gt;
&lt;p&gt;# Expected: a 4 KiB hole followed by the original data.
            rm -f /tmp/expected
            truncate -s 4K /tmp/expected
            cat /tmp/src &amp;gt;&amp;gt; /tmp/expected&lt;/p&gt;
&lt;p&gt;cp /tmp/src &amp;#34;$FILE&amp;#34;&lt;/p&gt;
&lt;p&gt;# Prime the page cache before moving data on the server.
            cat &amp;#34;$FILE&amp;#34; &amp;gt; /dev/null&lt;/p&gt;
&lt;p&gt;fallocate --insert-range -o 0 -l 4K &amp;#34;$FILE&amp;#34;&lt;/p&gt;
&lt;p&gt;if cmp -s /tmp/expected &amp;#34;$FILE&amp;#34;; th…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;smb/client: fix stale page cache in insert/collapse range&lt;/p&gt;
&lt;p&gt;smb3_insert_range() and smb3_collapse_range() use
truncate_pagecache_range() to invalidate the affected page cache.
However, if off or old_eof is not page-aligned, the boundary pages are
only partially zeroed and remain uptodate. As a result, the client may
return stale data after a successful insert/collapse range operation.&lt;/p&gt;
&lt;p&gt;For example, with 4K pages:&lt;/p&gt;
&lt;p&gt;page 0          page 1          page 2
    0------4K       4K------8K      8K------12K
       ^                                ^
    off=2K                       old_eof=10K&lt;/p&gt;
&lt;p&gt;Page 1 is removed from the page cache, while the boundary pages are
only partially zeroed. After COPYCHUNK moves the data on the server,
these cached pages may still return stale data.&lt;/p&gt;
&lt;p&gt;This can be reproduced on a CIFS mount:&lt;/p&gt;
&lt;p&gt;bash -c &amp;#39;
            FILE=/mnt/scratch/repro&lt;/p&gt;
&lt;p&gt;# Use a 6 KiB file so EOF is not page-aligned.
            dd if=/dev/urandom of=/tmp/src bs=1K count=6 status=none&lt;/p&gt;
&lt;p&gt;# Expected: a 4 KiB hole followed by the original data.
            rm -f /tmp/expected
            truncate -s 4K /tmp/expected
            cat /tmp/src &amp;gt;&amp;gt; /tmp/expected&lt;/p&gt;
&lt;p&gt;cp /tmp/src &amp;#34;$FILE&amp;#34;&lt;/p&gt;
&lt;p&gt;# Prime the page cache before moving data on the server.
            cat &amp;#34;$FILE&amp;#34; &amp;gt; /dev/null&lt;/p&gt;
&lt;p&gt;fallocate --insert-range -o 0 -l 4K &amp;#34;$FILE&amp;#34;&lt;/p&gt;
&lt;p&gt;if cmp -s /tmp/expected &amp;#34;$FILE&amp;#34;; th…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/fkie_cve-2026-98125</guid>
    </item>
    <item>
      <title>GHSA-mgrf-j38j-q2mg</title>
      <link>https://vulnerability.circl.lu/vuln/ghsa-mgrf-j38j-q2mg</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;smb/client: fix stale page cache in insert/collapse range&lt;/p&gt;
&lt;p&gt;smb3_insert_range() and smb3_collapse_range() use
truncate_pagecache_range() to invalidate the affected page cache.
However, if off or old_eof is not page-aligned, the boundary pages are
only partially zeroed and remain uptodate. As a result, the client may
return stale data after a successful insert/collapse range operation.&lt;/p&gt;
&lt;p&gt;For example, with 4K pages:&lt;/p&gt;
&lt;p&gt;page 0          page 1          page 2
    0------4K       4K------8K      8K------12K
       ^                                ^
    off=2K                       old_eof=10K&lt;/p&gt;
&lt;p&gt;Page 1 is removed from the page cache, while the boundary pages are
only partially zeroed. After COPYCHUNK moves the data on the server,
these cached pages may still return stale data.&lt;/p&gt;
&lt;p&gt;This can be reproduced on a CIFS mount:&lt;/p&gt;
&lt;p&gt;bash -c &amp;#39;
            FILE=/mnt/scratch/repro&lt;/p&gt;
&lt;p&gt;# Use a 6 KiB file so EOF is not page-aligned.
            dd if=/dev/urandom of=/tmp/src bs=1K count=6 status=none&lt;/p&gt;
&lt;p&gt;# Expected: a 4 KiB hole followed by the original data.
            rm -f /tmp/expected
            truncate -s 4K /tmp/expected
            cat /tmp/src &amp;gt;&amp;gt; /tmp/expected&lt;/p&gt;
&lt;p&gt;cp /tmp/src &amp;#34;$FILE&amp;#34;&lt;/p&gt;
&lt;p&gt;# Prime the page cache before moving data on the server.
            cat &amp;#34;$FILE&amp;#34; &amp;gt; /dev/null&lt;/p&gt;
&lt;p&gt;fallocate --insert-range -o 0 -l 4K &amp;#34;$FILE&amp;#34;&lt;/p&gt;
&lt;p&gt;if cmp -s /tmp/expected &amp;#34;$FILE&amp;#34;; th…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;smb/client: fix stale page cache in insert/collapse range&lt;/p&gt;
&lt;p&gt;smb3_insert_range() and smb3_collapse_range() use
truncate_pagecache_range() to invalidate the affected page cache.
However, if off or old_eof is not page-aligned, the boundary pages are
only partially zeroed and remain uptodate. As a result, the client may
return stale data after a successful insert/collapse range operation.&lt;/p&gt;
&lt;p&gt;For example, with 4K pages:&lt;/p&gt;
&lt;p&gt;page 0          page 1          page 2
    0------4K       4K------8K      8K------12K
       ^                                ^
    off=2K                       old_eof=10K&lt;/p&gt;
&lt;p&gt;Page 1 is removed from the page cache, while the boundary pages are
only partially zeroed. After COPYCHUNK moves the data on the server,
these cached pages may still return stale data.&lt;/p&gt;
&lt;p&gt;This can be reproduced on a CIFS mount:&lt;/p&gt;
&lt;p&gt;bash -c &amp;#39;
            FILE=/mnt/scratch/repro&lt;/p&gt;
&lt;p&gt;# Use a 6 KiB file so EOF is not page-aligned.
            dd if=/dev/urandom of=/tmp/src bs=1K count=6 status=none&lt;/p&gt;
&lt;p&gt;# Expected: a 4 KiB hole followed by the original data.
            rm -f /tmp/expected
            truncate -s 4K /tmp/expected
            cat /tmp/src &amp;gt;&amp;gt; /tmp/expected&lt;/p&gt;
&lt;p&gt;cp /tmp/src &amp;#34;$FILE&amp;#34;&lt;/p&gt;
&lt;p&gt;# Prime the page cache before moving data on the server.
            cat &amp;#34;$FILE&amp;#34; &amp;gt; /dev/null&lt;/p&gt;
&lt;p&gt;fallocate --insert-range -o 0 -l 4K &amp;#34;$FILE&amp;#34;&lt;/p&gt;
&lt;p&gt;if cmp -s /tmp/expected &amp;#34;$FILE&amp;#34;; th…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ghsa-mgrf-j38j-q2mg</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-98125</title>
      <link>https://vulnerability.circl.lu/vuln/ubuntu-cve-2026-98125</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux, Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, Ubuntu:Pro:16.04:LTS: linux, Ubuntu:Pro:16.04:LTS: linux-aws, Ubuntu:Pro:16.04:LTS: linux-aws-hwe, Ubuntu:Pro:16.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-gcp, Ubuntu:Pro:16.04:LTS: linux-hwe and 246 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: smb/client: fix stale page cache in insert/collapse range smb3_insert_range() and smb3_collapse_range() use truncate_pagecache_range() to invalidate the affected page cache. However, if off or old_eof is not page-aligned, the boundary pages are only partially zeroed and remain uptodate. As a result, the client may return stale data after a successful insert/collapse range operation. For example, with 4K pages:     page 0          page 1          page 2     0------4K       4K------8K      8K------12K        ^                                ^     off=2K                       old_eof=10K Page 1 is removed from the page cache, while the boundary pages are only partially zeroed. After COPYCHUNK moves the data on the server, these cached pages may still return stale data. This can be reproduced on a CIFS mount:     bash -c &amp;#39;             FILE=/mnt/scratch/repro             # Use a 6 KiB file so EOF is not page-aligned.             dd if=/dev/urandom of=/tmp/src bs=1K count=6 status=none             # Expected: a 4 KiB hole followed by the original data.             rm -f /tmp/expected             truncate -s 4K /tmp/expected             cat /tmp/src &amp;gt;&amp;gt; /tmp/expected             cp /tmp/src &amp;#34;$FILE&amp;#34;             # Prime the page cache before moving data on the server.             cat &amp;#34;$FILE&amp;#34; &amp;gt; /dev/null             fallocate --insert-range -o 0 -l 4K &amp;#34;$FILE&amp;#34;             if cmp -s /tmp/expected &amp;#34;$FILE&amp;#34;; then…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux, Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, Ubuntu:Pro:16.04:LTS: linux, Ubuntu:Pro:16.04:LTS: linux-aws, Ubuntu:Pro:16.04:LTS: linux-aws-hwe, Ubuntu:Pro:16.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-gcp, Ubuntu:Pro:16.04:LTS: linux-hwe and 246 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: smb/client: fix stale page cache in insert/collapse range smb3_insert_range() and smb3_collapse_range() use truncate_pagecache_range() to invalidate the affected page cache. However, if off or old_eof is not page-aligned, the boundary pages are only partially zeroed and remain uptodate. As a result, the client may return stale data after a successful insert/collapse range operation. For example, with 4K pages:     page 0          page 1          page 2     0------4K       4K------8K      8K------12K        ^                                ^     off=2K                       old_eof=10K Page 1 is removed from the page cache, while the boundary pages are only partially zeroed. After COPYCHUNK moves the data on the server, these cached pages may still return stale data. This can be reproduced on a CIFS mount:     bash -c &amp;#39;             FILE=/mnt/scratch/repro             # Use a 6 KiB file so EOF is not page-aligned.             dd if=/dev/urandom of=/tmp/src bs=1K count=6 status=none             # Expected: a 4 KiB hole followed by the original data.             rm -f /tmp/expected             truncate -s 4K /tmp/expected             cat /tmp/src &amp;gt;&amp;gt; /tmp/expected             cp /tmp/src &amp;#34;$FILE&amp;#34;             # Prime the page cache before moving data on the server.             cat &amp;#34;$FILE&amp;#34; &amp;gt; /dev/null             fallocate --insert-range -o 0 -l 4K &amp;#34;$FILE&amp;#34;             if cmp -s /tmp/expected &amp;#34;$FILE&amp;#34;; then…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ubuntu-cve-2026-98125</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-3579 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://vulnerability.circl.lu/vuln/wid-sec-w-2026-3579</link>
      <description>&lt;p&gt;Ein lokaler Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Zustand herbeizuführen oder nicht näher spezifizierten Angriff durchzuführen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein lokaler Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Zustand herbeizuführen oder nicht näher spezifizierten Angriff durchzuführen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/wid-sec-w-2026-3579</guid>
    </item>
  </channel>
</rss>
