<?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://cve.radiocsirt.org</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, 16 Nov 2026 18:16:03 +0000</lastBuildDate>
    <item>
      <title>ALSA-2026:95367 — Important: kernel security update</title>
      <link>https://cve.radiocsirt.org/vuln/alsa-2026:95367</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; AlmaLinux:10: kernel-abi-stablelists, AlmaLinux:10: kernel-doc&lt;/p&gt;
&lt;p&gt;The kernel packages contain the Linux kernel, the core of any Linux operating system.&lt;/p&gt;
&lt;p&gt;Security Fix(es):&lt;/p&gt;
&lt;p&gt;* kernel: writeback: fix race between cgroup_writeback_umount() and inode_switch_wbs() (CVE-2026-64378)
  * kernel: sunrpc: pin svc_xprt across the asynchronous TLS handshake callback (CVE-2026-72222)
  * kernel: sunrpc: wait for in-flight TLS handshake callback when cancel loses race (CVE-2026-72221)
  * kernel: fs/resctrl: Fix use-after-free during unmount (CVE-2026-72080)
  * kernel: sctp: clear new_transport when removing a peer (CVE-2026-74586)
  * kernel: openvswitch: Fix CT limit teardown use-after-free (CVE-2026-89488)
  * kernel: PCI/sysfs: Add lockdown checks to legacy I/O and memory handlers (CVE-2026-90315)
  * kernel: kernel: xfs: Unauthorized data modification via improper file size exchange handling (CVE-2026-98974)&lt;/p&gt;
&lt;p&gt;For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; AlmaLinux:10: kernel-abi-stablelists, AlmaLinux:10: kernel-doc&lt;/p&gt;
&lt;p&gt;The kernel packages contain the Linux kernel, the core of any Linux operating system.&lt;/p&gt;
&lt;p&gt;Security Fix(es):&lt;/p&gt;
&lt;p&gt;* kernel: writeback: fix race between cgroup_writeback_umount() and inode_switch_wbs() (CVE-2026-64378)
  * kernel: sunrpc: pin svc_xprt across the asynchronous TLS handshake callback (CVE-2026-72222)
  * kernel: sunrpc: wait for in-flight TLS handshake callback when cancel loses race (CVE-2026-72221)
  * kernel: fs/resctrl: Fix use-after-free during unmount (CVE-2026-72080)
  * kernel: sctp: clear new_transport when removing a peer (CVE-2026-74586)
  * kernel: openvswitch: Fix CT limit teardown use-after-free (CVE-2026-89488)
  * kernel: PCI/sysfs: Add lockdown checks to legacy I/O and memory handlers (CVE-2026-90315)
  * kernel: kernel: xfs: Unauthorized data modification via improper file size exchange handling (CVE-2026-98974)&lt;/p&gt;
&lt;p&gt;For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/alsa-2026:95367</guid>
    </item>
    <item>
      <title>BELL-CVE-2026-98974</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2026-98974</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bell-cve-2026-98974</guid>
    </item>
    <item>
      <title>certfr-2026-avi-1471 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de Red Hat. Certaines d'entre elles permettent à un…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2026-avi-1471</link>
      <description>certfr-2026-avi-1471</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2026-avi-1471</guid>
    </item>
    <item>
      <title>EUVD-2026-392019</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-392019</link>
      <description>EUVD-2026-392019</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-392019</guid>
    </item>
    <item>
      <title>fkie_cve-2026-98974</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-98974</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;xfs: fix exchange-range-to-eof file size exchange&lt;/p&gt;
&lt;p&gt;Norbert Szetei posted a patch containing an incomplete description of a
bug in XFS_IOC_EXCHANGE_RANGE&amp;#39;s TO_EOF flag.  The bug tricks
exchange-range into modifying a file so that it has shared blocks
starting beyond EOF, which is never allowed because files never have
written data beyond EOF, and you can only share written data blocks.
This is key to all the incorrect behavior that follows.&lt;/p&gt;
&lt;p&gt;Eventually I got from Norbert a description of what&amp;#39;s going wrong:&lt;/p&gt;
&lt;p&gt;&amp;gt; Fair. Here it is with physical block numbers, 4k blocks. peer is the file
&amp;gt; that gets rewritten and file1 is the one that ends up with the flag
&amp;gt; cleared.
&amp;gt;
&amp;gt; Start, nothing shared:
&amp;gt;
&amp;gt;	peer size 4096   -&amp;gt; [100]
&amp;gt;	file1 size 12288 -&amp;gt; [200] [201] [202]
&amp;gt;	donor1 size 4096 -&amp;gt; [300]
&amp;gt;	donor2 size 4096 -&amp;gt; [400]
&amp;gt;
&amp;gt; 1. FICLONERANGE peer&amp;#39;s block into file1&amp;#39;s middle slot:
&amp;gt;
&amp;gt;	peer size 4096   -&amp;gt; [100]
&amp;gt;	file1 size 12288 -&amp;gt; [200] [100] [202] reflink flag set
&amp;gt;                             ^^^^^ both files own block 100
&amp;gt;
&amp;gt; 2. XFS_IOC_EXCHANGE_RANGE file1 against donor1, file1_offset 0,
&amp;gt; file2_offset 8192, length 0, TO_EOF. One block is exchanged, and the sizes
&amp;gt; are exchanged with it:
&amp;gt;
&amp;gt;	file1 size 4096   -&amp;gt; [200] [100] [300] reflink flag set
&amp;gt;                              ^^^^^^^^^^^ still owned, now past the size
&amp;gt;	donor1 size 12288 -&amp;gt; [202]
&amp;gt;
&amp;gt; file1 says it is one block long while it still owns three. Noth…&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;xfs: fix exchange-range-to-eof file size exchange&lt;/p&gt;
&lt;p&gt;Norbert Szetei posted a patch containing an incomplete description of a
bug in XFS_IOC_EXCHANGE_RANGE&amp;#39;s TO_EOF flag.  The bug tricks
exchange-range into modifying a file so that it has shared blocks
starting beyond EOF, which is never allowed because files never have
written data beyond EOF, and you can only share written data blocks.
This is key to all the incorrect behavior that follows.&lt;/p&gt;
&lt;p&gt;Eventually I got from Norbert a description of what&amp;#39;s going wrong:&lt;/p&gt;
&lt;p&gt;&amp;gt; Fair. Here it is with physical block numbers, 4k blocks. peer is the file
&amp;gt; that gets rewritten and file1 is the one that ends up with the flag
&amp;gt; cleared.
&amp;gt;
&amp;gt; Start, nothing shared:
&amp;gt;
&amp;gt;	peer size 4096   -&amp;gt; [100]
&amp;gt;	file1 size 12288 -&amp;gt; [200] [201] [202]
&amp;gt;	donor1 size 4096 -&amp;gt; [300]
&amp;gt;	donor2 size 4096 -&amp;gt; [400]
&amp;gt;
&amp;gt; 1. FICLONERANGE peer&amp;#39;s block into file1&amp;#39;s middle slot:
&amp;gt;
&amp;gt;	peer size 4096   -&amp;gt; [100]
&amp;gt;	file1 size 12288 -&amp;gt; [200] [100] [202] reflink flag set
&amp;gt;                             ^^^^^ both files own block 100
&amp;gt;
&amp;gt; 2. XFS_IOC_EXCHANGE_RANGE file1 against donor1, file1_offset 0,
&amp;gt; file2_offset 8192, length 0, TO_EOF. One block is exchanged, and the sizes
&amp;gt; are exchanged with it:
&amp;gt;
&amp;gt;	file1 size 4096   -&amp;gt; [200] [100] [300] reflink flag set
&amp;gt;                              ^^^^^^^^^^^ still owned, now past the size
&amp;gt;	donor1 size 12288 -&amp;gt; [202]
&amp;gt;
&amp;gt; file1 says it is one block long while it still owns three. Noth…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-98974</guid>
    </item>
    <item>
      <title>GHSA-2g9r-fc27-29gx</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-2g9r-fc27-29gx</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;xfs: fix exchange-range-to-eof file size exchange&lt;/p&gt;
&lt;p&gt;Norbert Szetei posted a patch containing an incomplete description of a
bug in XFS_IOC_EXCHANGE_RANGE&amp;#39;s TO_EOF flag.  The bug tricks
exchange-range into modifying a file so that it has shared blocks
starting beyond EOF, which is never allowed because files never have
written data beyond EOF, and you can only share written data blocks.
This is key to all the incorrect behavior that follows.&lt;/p&gt;
&lt;p&gt;Eventually I got from Norbert a description of what&amp;#39;s going wrong:&lt;/p&gt;
&lt;p&gt;&amp;gt; Fair. Here it is with physical block numbers, 4k blocks. peer is the file
&amp;gt; that gets rewritten and file1 is the one that ends up with the flag
&amp;gt; cleared.
&amp;gt;
&amp;gt; Start, nothing shared:
&amp;gt;
&amp;gt;	peer size 4096   -&amp;gt; [100]
&amp;gt;	file1 size 12288 -&amp;gt; [200] [201] [202]
&amp;gt;	donor1 size 4096 -&amp;gt; [300]
&amp;gt;	donor2 size 4096 -&amp;gt; [400]
&amp;gt;
&amp;gt; 1. FICLONERANGE peer&amp;#39;s block into file1&amp;#39;s middle slot:
&amp;gt;
&amp;gt;	peer size 4096   -&amp;gt; [100]
&amp;gt;	file1 size 12288 -&amp;gt; [200] [100] [202] reflink flag set
&amp;gt;                             ^^^^^ both files own block 100
&amp;gt;
&amp;gt; 2. XFS_IOC_EXCHANGE_RANGE file1 against donor1, file1_offset 0,
&amp;gt; file2_offset 8192, length 0, TO_EOF. One block is exchanged, and the sizes
&amp;gt; are exchanged with it:
&amp;gt;
&amp;gt;	file1 size 4096   -&amp;gt; [200] [100] [300] reflink flag set
&amp;gt;                              ^^^^^^^^^^^ still owned, now past the size
&amp;gt;	donor1 size 12288 -&amp;gt; [202]
&amp;gt;
&amp;gt; file1 says it is one block long while it still owns three. Noth…&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;xfs: fix exchange-range-to-eof file size exchange&lt;/p&gt;
&lt;p&gt;Norbert Szetei posted a patch containing an incomplete description of a
bug in XFS_IOC_EXCHANGE_RANGE&amp;#39;s TO_EOF flag.  The bug tricks
exchange-range into modifying a file so that it has shared blocks
starting beyond EOF, which is never allowed because files never have
written data beyond EOF, and you can only share written data blocks.
This is key to all the incorrect behavior that follows.&lt;/p&gt;
&lt;p&gt;Eventually I got from Norbert a description of what&amp;#39;s going wrong:&lt;/p&gt;
&lt;p&gt;&amp;gt; Fair. Here it is with physical block numbers, 4k blocks. peer is the file
&amp;gt; that gets rewritten and file1 is the one that ends up with the flag
&amp;gt; cleared.
&amp;gt;
&amp;gt; Start, nothing shared:
&amp;gt;
&amp;gt;	peer size 4096   -&amp;gt; [100]
&amp;gt;	file1 size 12288 -&amp;gt; [200] [201] [202]
&amp;gt;	donor1 size 4096 -&amp;gt; [300]
&amp;gt;	donor2 size 4096 -&amp;gt; [400]
&amp;gt;
&amp;gt; 1. FICLONERANGE peer&amp;#39;s block into file1&amp;#39;s middle slot:
&amp;gt;
&amp;gt;	peer size 4096   -&amp;gt; [100]
&amp;gt;	file1 size 12288 -&amp;gt; [200] [100] [202] reflink flag set
&amp;gt;                             ^^^^^ both files own block 100
&amp;gt;
&amp;gt; 2. XFS_IOC_EXCHANGE_RANGE file1 against donor1, file1_offset 0,
&amp;gt; file2_offset 8192, length 0, TO_EOF. One block is exchanged, and the sizes
&amp;gt; are exchanged with it:
&amp;gt;
&amp;gt;	file1 size 4096   -&amp;gt; [200] [100] [300] reflink flag set
&amp;gt;                              ^^^^^^^^^^^ still owned, now past the size
&amp;gt;	donor1 size 12288 -&amp;gt; [202]
&amp;gt;
&amp;gt; file1 says it is one block long while it still owns three. Noth…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-2g9r-fc27-29gx</guid>
    </item>
    <item>
      <title>msrc_CVE-2026-98974 — xfs: fix exchange-range-to-eof file size exchange</title>
      <link>https://cve.radiocsirt.org/vuln/msrc_cve-2026-98974</link>
      <description>msrc_CVE-2026-98974</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/msrc_cve-2026-98974</guid>
    </item>
    <item>
      <title>RHSA-2026:95367 — Red Hat Security Advisory: kernel security update</title>
      <link>https://cve.radiocsirt.org/vuln/rhsa-2026:95367</link>
      <description>&lt;p&gt;kernel: writeback: fix race between cgroup_writeback_umount() and inode_switch_wbs() kernel: fs/resctrl: Fix use-after-free during unmount kernel: sunrpc: wait for in-flight TLS handshake callback when cancel loses race kernel: sunrpc: pin svc_xprt across the asynchronous TLS handshake callback kernel: sctp: clear new_transport when removing a peer kernel: openvswitch: Fix CT limit teardown use-after-free kernel: PCI/sysfs: Add lockdown checks to legacy I/O and memory handlers kernel: kernel: xfs: Unauthorized data modification via improper file size exchange handling&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;kernel: writeback: fix race between cgroup_writeback_umount() and inode_switch_wbs() kernel: fs/resctrl: Fix use-after-free during unmount kernel: sunrpc: wait for in-flight TLS handshake callback when cancel loses race kernel: sunrpc: pin svc_xprt across the asynchronous TLS handshake callback kernel: sctp: clear new_transport when removing a peer kernel: openvswitch: Fix CT limit teardown use-after-free kernel: PCI/sysfs: Add lockdown checks to legacy I/O and memory handlers kernel: kernel: xfs: Unauthorized data modification via improper file size exchange handling&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/rhsa-2026:95367</guid>
    </item>
    <item>
      <title>RLSA-2026:95367 — Important: kernel security update</title>
      <link>https://cve.radiocsirt.org/vuln/rlsa-2026:95367</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Rocky Linux:10: kernel&lt;/p&gt;
&lt;p&gt;The kernel packages contain the Linux kernel, the core of any Linux operating system.&lt;/p&gt;
&lt;p&gt;Security Fix(es):&lt;/p&gt;
&lt;p&gt;* kernel: writeback: fix race between cgroup_writeback_umount() and inode_switch_wbs() (CVE-2026-64378)&lt;/p&gt;
&lt;p&gt;* kernel: sunrpc: pin svc_xprt across the asynchronous TLS handshake callback (CVE-2026-72222)&lt;/p&gt;
&lt;p&gt;* kernel: sunrpc: wait for in-flight TLS handshake callback when cancel loses race (CVE-2026-72221)&lt;/p&gt;
&lt;p&gt;* kernel: fs/resctrl: Fix use-after-free during unmount (CVE-2026-72080)&lt;/p&gt;
&lt;p&gt;* kernel: sctp: clear new_transport when removing a peer (CVE-2026-74586)&lt;/p&gt;
&lt;p&gt;* kernel: openvswitch: Fix CT limit teardown use-after-free (CVE-2026-89488)&lt;/p&gt;
&lt;p&gt;* kernel: PCI/sysfs: Add lockdown checks to legacy I/O and memory handlers (CVE-2026-90315)&lt;/p&gt;
&lt;p&gt;* kernel: kernel: xfs: Unauthorized data modification via improper file size exchange handling (CVE-2026-98974)&lt;/p&gt;
&lt;p&gt;For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Rocky Linux:10: kernel&lt;/p&gt;
&lt;p&gt;The kernel packages contain the Linux kernel, the core of any Linux operating system.&lt;/p&gt;
&lt;p&gt;Security Fix(es):&lt;/p&gt;
&lt;p&gt;* kernel: writeback: fix race between cgroup_writeback_umount() and inode_switch_wbs() (CVE-2026-64378)&lt;/p&gt;
&lt;p&gt;* kernel: sunrpc: pin svc_xprt across the asynchronous TLS handshake callback (CVE-2026-72222)&lt;/p&gt;
&lt;p&gt;* kernel: sunrpc: wait for in-flight TLS handshake callback when cancel loses race (CVE-2026-72221)&lt;/p&gt;
&lt;p&gt;* kernel: fs/resctrl: Fix use-after-free during unmount (CVE-2026-72080)&lt;/p&gt;
&lt;p&gt;* kernel: sctp: clear new_transport when removing a peer (CVE-2026-74586)&lt;/p&gt;
&lt;p&gt;* kernel: openvswitch: Fix CT limit teardown use-after-free (CVE-2026-89488)&lt;/p&gt;
&lt;p&gt;* kernel: PCI/sysfs: Add lockdown checks to legacy I/O and memory handlers (CVE-2026-90315)&lt;/p&gt;
&lt;p&gt;* kernel: kernel: xfs: Unauthorized data modification via improper file size exchange handling (CVE-2026-98974)&lt;/p&gt;
&lt;p&gt;For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/rlsa-2026:95367</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-98974</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-98974</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3, Ubuntu:18.04:LTS: linux-gke-4.15, Ubuntu:18.04:LTS: linux-gke-5.4 and 129 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: xfs: fix exchange-range-to-eof file size exchange Norbert Szetei posted a patch containing an incomplete description of a bug in XFS_IOC_EXCHANGE_RANGE&amp;#39;s TO_EOF flag.  The bug tricks exchange-range into modifying a file so that it has shared blocks starting beyond EOF, which is never allowed because files never have written data beyond EOF, and you can only share written data blocks. This is key to all the incorrect behavior that follows. Eventually I got from Norbert a description of what&amp;#39;s going wrong: &amp;gt; Fair. Here it is with physical block numbers, 4k blocks. peer is the file &amp;gt; that gets rewritten and file1 is the one that ends up with the flag &amp;gt; cleared. &amp;gt; &amp;gt; Start, nothing shared: &amp;gt; &amp;gt;	peer size 4096   -&amp;gt; [100] &amp;gt;	file1 size 12288 -&amp;gt; [200] [201] [202] &amp;gt;	donor1 size 4096 -&amp;gt; [300] &amp;gt;	donor2 size 4096 -&amp;gt; [400] &amp;gt; &amp;gt; 1. FICLONERANGE peer&amp;#39;s block into file1&amp;#39;s middle slot: &amp;gt; &amp;gt;	peer size 4096   -&amp;gt; [100] &amp;gt;	file1 size 12288 -&amp;gt; [200] [100] [202] reflink flag set &amp;gt;                             ^^^^^ both files own block 100 &amp;gt; &amp;gt; 2. XFS_IOC_EXCHANGE_RANGE file1 against donor1, file1_offset 0, &amp;gt; file2_offset 8192, length 0, TO_EOF. One block is exchanged, and the sizes &amp;gt; are exchanged with it: &amp;gt; &amp;gt;	file1 size 4096   -&amp;gt; [200] [100] [300] reflink flag set &amp;gt;                              ^^^^^^^^^^^ still owned, now past the size &amp;gt;	donor1 size 12288 -&amp;gt; [202] &amp;gt; &amp;gt; file1 says it is one block long while it still owns three. Nothing…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3, Ubuntu:18.04:LTS: linux-gke-4.15, Ubuntu:18.04:LTS: linux-gke-5.4 and 129 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: xfs: fix exchange-range-to-eof file size exchange Norbert Szetei posted a patch containing an incomplete description of a bug in XFS_IOC_EXCHANGE_RANGE&amp;#39;s TO_EOF flag.  The bug tricks exchange-range into modifying a file so that it has shared blocks starting beyond EOF, which is never allowed because files never have written data beyond EOF, and you can only share written data blocks. This is key to all the incorrect behavior that follows. Eventually I got from Norbert a description of what&amp;#39;s going wrong: &amp;gt; Fair. Here it is with physical block numbers, 4k blocks. peer is the file &amp;gt; that gets rewritten and file1 is the one that ends up with the flag &amp;gt; cleared. &amp;gt; &amp;gt; Start, nothing shared: &amp;gt; &amp;gt;	peer size 4096   -&amp;gt; [100] &amp;gt;	file1 size 12288 -&amp;gt; [200] [201] [202] &amp;gt;	donor1 size 4096 -&amp;gt; [300] &amp;gt;	donor2 size 4096 -&amp;gt; [400] &amp;gt; &amp;gt; 1. FICLONERANGE peer&amp;#39;s block into file1&amp;#39;s middle slot: &amp;gt; &amp;gt;	peer size 4096   -&amp;gt; [100] &amp;gt;	file1 size 12288 -&amp;gt; [200] [100] [202] reflink flag set &amp;gt;                             ^^^^^ both files own block 100 &amp;gt; &amp;gt; 2. XFS_IOC_EXCHANGE_RANGE file1 against donor1, file1_offset 0, &amp;gt; file2_offset 8192, length 0, TO_EOF. One block is exchanged, and the sizes &amp;gt; are exchanged with it: &amp;gt; &amp;gt;	file1 size 4096   -&amp;gt; [200] [100] [300] reflink flag set &amp;gt;                              ^^^^^^^^^^^ still owned, now past the size &amp;gt;	donor1 size 12288 -&amp;gt; [202] &amp;gt; &amp;gt; file1 says it is one block long while it still owns three. Nothing…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-98974</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-4152 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-4152</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen, möglicherweise einen Denial-of-Service-Angriff auszulösen, Daten zu manipulieren oder offenzulegen oder Sicherheitsmaßnahmen zu umgehen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen, möglicherweise einen Denial-of-Service-Angriff auszulösen, Daten zu manipulieren oder offenzulegen oder Sicherheitsmaßnahmen zu umgehen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2026-4152</guid>
    </item>
  </channel>
</rss>
