<?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 19:00:47 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-98124</title>
      <link>https://vulnerability.circl.lu/vuln/fkie_cve-2026-98124</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;smb/client: invalidate fscache for fallocate range operations&lt;/p&gt;
&lt;p&gt;smb3_zero_range(), smb3_punch_hole(), smb3_insert_range(), and
smb3_collapse_range() modify file contents through server-side range
operations. These operations discard the affected page cache, but leave
the FS-Cache cookie valid, so a later read may return data cached before
the range operation.&lt;/p&gt;
&lt;p&gt;Fix this by invalidating FS-Cache after outstanding I/O has completed
and before modifying the file on the server.&lt;/p&gt;
&lt;p&gt;Run the following as root on a CIFS mount with fsc enabled and an active
CacheFiles backend:&lt;/p&gt;
&lt;p&gt;bash -c &amp;#39;
                MNT=/mnt/cifs
                FILE=&amp;#34;$MNT/repro&amp;#34;&lt;/p&gt;
&lt;p&gt;# Generate four 1 MiB random blocks: [A][B][C][D].
                dd if=/dev/urandom of=/tmp/src bs=1M count=4 status=none&lt;/p&gt;
&lt;p&gt;# Expected contents after zeroing B: [A][zero][C][D].
                cp /tmp/src /tmp/expected
                dd if=/dev/zero of=/tmp/expected bs=1M seek=1 count=1 \
                        conv=notrunc status=none
                cp /tmp/src &amp;#34;$FILE&amp;#34;&lt;/p&gt;
&lt;p&gt;# Populate FS-Cache, then discard the page cache.
                sync
                echo 1 &amp;gt; /proc/sys/vm/drop_caches
                cat &amp;#34;$FILE&amp;#34; &amp;gt; /dev/null
                sync
                echo 1 &amp;gt; /proc/sys/vm/drop_caches&lt;/p&gt;
&lt;p&gt;fallocate --zero-range -o 1M -l 1M &amp;#34;$FILE&amp;#34;&lt;/p&gt;
&lt;p&gt;if cmp -s /tmp/expected &amp;#34;$FILE&amp;#34;; then…&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: invalidate fscache for fallocate range operations&lt;/p&gt;
&lt;p&gt;smb3_zero_range(), smb3_punch_hole(), smb3_insert_range(), and
smb3_collapse_range() modify file contents through server-side range
operations. These operations discard the affected page cache, but leave
the FS-Cache cookie valid, so a later read may return data cached before
the range operation.&lt;/p&gt;
&lt;p&gt;Fix this by invalidating FS-Cache after outstanding I/O has completed
and before modifying the file on the server.&lt;/p&gt;
&lt;p&gt;Run the following as root on a CIFS mount with fsc enabled and an active
CacheFiles backend:&lt;/p&gt;
&lt;p&gt;bash -c &amp;#39;
                MNT=/mnt/cifs
                FILE=&amp;#34;$MNT/repro&amp;#34;&lt;/p&gt;
&lt;p&gt;# Generate four 1 MiB random blocks: [A][B][C][D].
                dd if=/dev/urandom of=/tmp/src bs=1M count=4 status=none&lt;/p&gt;
&lt;p&gt;# Expected contents after zeroing B: [A][zero][C][D].
                cp /tmp/src /tmp/expected
                dd if=/dev/zero of=/tmp/expected bs=1M seek=1 count=1 \
                        conv=notrunc status=none
                cp /tmp/src &amp;#34;$FILE&amp;#34;&lt;/p&gt;
&lt;p&gt;# Populate FS-Cache, then discard the page cache.
                sync
                echo 1 &amp;gt; /proc/sys/vm/drop_caches
                cat &amp;#34;$FILE&amp;#34; &amp;gt; /dev/null
                sync
                echo 1 &amp;gt; /proc/sys/vm/drop_caches&lt;/p&gt;
&lt;p&gt;fallocate --zero-range -o 1M -l 1M &amp;#34;$FILE&amp;#34;&lt;/p&gt;
&lt;p&gt;if cmp -s /tmp/expected &amp;#34;$FILE&amp;#34;; then…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/fkie_cve-2026-98124</guid>
    </item>
    <item>
      <title>GHSA-wcf3-p4hx-gg65</title>
      <link>https://vulnerability.circl.lu/vuln/ghsa-wcf3-p4hx-gg65</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;smb/client: invalidate fscache for fallocate range operations&lt;/p&gt;
&lt;p&gt;smb3_zero_range(), smb3_punch_hole(), smb3_insert_range(), and
smb3_collapse_range() modify file contents through server-side range
operations. These operations discard the affected page cache, but leave
the FS-Cache cookie valid, so a later read may return data cached before
the range operation.&lt;/p&gt;
&lt;p&gt;Fix this by invalidating FS-Cache after outstanding I/O has completed
and before modifying the file on the server.&lt;/p&gt;
&lt;p&gt;Run the following as root on a CIFS mount with fsc enabled and an active
CacheFiles backend:&lt;/p&gt;
&lt;p&gt;bash -c &amp;#39;
                MNT=/mnt/cifs
                FILE=&amp;#34;$MNT/repro&amp;#34;&lt;/p&gt;
&lt;p&gt;# Generate four 1 MiB random blocks: [A][B][C][D].
                dd if=/dev/urandom of=/tmp/src bs=1M count=4 status=none&lt;/p&gt;
&lt;p&gt;# Expected contents after zeroing B: [A][zero][C][D].
                cp /tmp/src /tmp/expected
                dd if=/dev/zero of=/tmp/expected bs=1M seek=1 count=1 \
                        conv=notrunc status=none
                cp /tmp/src &amp;#34;$FILE&amp;#34;&lt;/p&gt;
&lt;p&gt;# Populate FS-Cache, then discard the page cache.
                sync
                echo 1 &amp;gt; /proc/sys/vm/drop_caches
                cat &amp;#34;$FILE&amp;#34; &amp;gt; /dev/null
                sync
                echo 1 &amp;gt; /proc/sys/vm/drop_caches&lt;/p&gt;
&lt;p&gt;fallocate --zero-range -o 1M -l 1M &amp;#34;$FILE&amp;#34;&lt;/p&gt;
&lt;p&gt;if cmp -s /tmp/expected &amp;#34;$FILE&amp;#34;; then…&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: invalidate fscache for fallocate range operations&lt;/p&gt;
&lt;p&gt;smb3_zero_range(), smb3_punch_hole(), smb3_insert_range(), and
smb3_collapse_range() modify file contents through server-side range
operations. These operations discard the affected page cache, but leave
the FS-Cache cookie valid, so a later read may return data cached before
the range operation.&lt;/p&gt;
&lt;p&gt;Fix this by invalidating FS-Cache after outstanding I/O has completed
and before modifying the file on the server.&lt;/p&gt;
&lt;p&gt;Run the following as root on a CIFS mount with fsc enabled and an active
CacheFiles backend:&lt;/p&gt;
&lt;p&gt;bash -c &amp;#39;
                MNT=/mnt/cifs
                FILE=&amp;#34;$MNT/repro&amp;#34;&lt;/p&gt;
&lt;p&gt;# Generate four 1 MiB random blocks: [A][B][C][D].
                dd if=/dev/urandom of=/tmp/src bs=1M count=4 status=none&lt;/p&gt;
&lt;p&gt;# Expected contents after zeroing B: [A][zero][C][D].
                cp /tmp/src /tmp/expected
                dd if=/dev/zero of=/tmp/expected bs=1M seek=1 count=1 \
                        conv=notrunc status=none
                cp /tmp/src &amp;#34;$FILE&amp;#34;&lt;/p&gt;
&lt;p&gt;# Populate FS-Cache, then discard the page cache.
                sync
                echo 1 &amp;gt; /proc/sys/vm/drop_caches
                cat &amp;#34;$FILE&amp;#34; &amp;gt; /dev/null
                sync
                echo 1 &amp;gt; /proc/sys/vm/drop_caches&lt;/p&gt;
&lt;p&gt;fallocate --zero-range -o 1M -l 1M &amp;#34;$FILE&amp;#34;&lt;/p&gt;
&lt;p&gt;if cmp -s /tmp/expected &amp;#34;$FILE&amp;#34;; then…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ghsa-wcf3-p4hx-gg65</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-98124</title>
      <link>https://vulnerability.circl.lu/vuln/ubuntu-cve-2026-98124</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: invalidate fscache for fallocate range operations smb3_zero_range(), smb3_punch_hole(), smb3_insert_range(), and smb3_collapse_range() modify file contents through server-side range operations. These operations discard the affected page cache, but leave the FS-Cache cookie valid, so a later read may return data cached before the range operation. Fix this by invalidating FS-Cache after outstanding I/O has completed and before modifying the file on the server. Run the following as root on a CIFS mount with fsc enabled and an active CacheFiles backend:         bash -c &amp;#39;                 MNT=/mnt/cifs                 FILE=&amp;#34;$MNT/repro&amp;#34;                 # Generate four 1 MiB random blocks: [A][B][C][D].                 dd if=/dev/urandom of=/tmp/src bs=1M count=4 status=none                 # Expected contents after zeroing B: [A][zero][C][D].                 cp /tmp/src /tmp/expected                 dd if=/dev/zero of=/tmp/expected bs=1M seek=1 count=1 \                         conv=notrunc status=none                 cp /tmp/src &amp;#34;$FILE&amp;#34;                 # Populate FS-Cache, then discard the page cache.                 sync                 echo 1 &amp;gt; /proc/sys/vm/drop_caches                 cat &amp;#34;$FILE&amp;#34; &amp;gt; /dev/null                 sync                 echo 1 &amp;gt; /proc/sys/vm/drop_caches                 fallocate --zero-range -o 1M -l 1M &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: invalidate fscache for fallocate range operations smb3_zero_range(), smb3_punch_hole(), smb3_insert_range(), and smb3_collapse_range() modify file contents through server-side range operations. These operations discard the affected page cache, but leave the FS-Cache cookie valid, so a later read may return data cached before the range operation. Fix this by invalidating FS-Cache after outstanding I/O has completed and before modifying the file on the server. Run the following as root on a CIFS mount with fsc enabled and an active CacheFiles backend:         bash -c &amp;#39;                 MNT=/mnt/cifs                 FILE=&amp;#34;$MNT/repro&amp;#34;                 # Generate four 1 MiB random blocks: [A][B][C][D].                 dd if=/dev/urandom of=/tmp/src bs=1M count=4 status=none                 # Expected contents after zeroing B: [A][zero][C][D].                 cp /tmp/src /tmp/expected                 dd if=/dev/zero of=/tmp/expected bs=1M seek=1 count=1 \                         conv=notrunc status=none                 cp /tmp/src &amp;#34;$FILE&amp;#34;                 # Populate FS-Cache, then discard the page cache.                 sync                 echo 1 &amp;gt; /proc/sys/vm/drop_caches                 cat &amp;#34;$FILE&amp;#34; &amp;gt; /dev/null                 sync                 echo 1 &amp;gt; /proc/sys/vm/drop_caches                 fallocate --zero-range -o 1M -l 1M &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-98124</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>
