<?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://db.gcve.eu</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>Wed, 11 Nov 2026 16:47:22 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-98974 — xfs: fix exchange-range-to-eof file size exchange</title>
      <link>https://db.gcve.eu/vuln/cve-2026-98974</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&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;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&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://db.gcve.eu/vuln/cve-2026-98974</guid>
    </item>
    <item>
      <title>USN-9018-1 — linux, linux-aws, linux-gcp, linux-ibm, linux-oem-7.0, linux-oracle vulnerabilities</title>
      <link>https://db.gcve.eu/vuln/usn-9018-1</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:26.04:LTS: linux, Ubuntu:26.04:LTS: linux-aws, Ubuntu:26.04:LTS: linux-gcp, Ubuntu:26.04:LTS: linux-ibm, Ubuntu:26.04:LTS: linux-oem-7.0, Ubuntu:26.04:LTS: linux-oracle&lt;/p&gt;
&lt;p&gt;Several security issues were discovered in the Linux kernel.
An attacker could possibly use these to compromise the system.
This update corrects flaws in the following subsystems:
  - Network file systems library;
  - Stream parser;
  - ARM64 architecture;
  - PowerPC architecture;
  - RISC-V architecture;
  - S390 architecture;
  - User-Mode Linux (UML);
  - x86 architecture;
  - Block layer subsystem;
  - Android drivers;
  - Bluetooth drivers;
  - TPM device driver;
  - DPLL subsystem;
  - EDAC drivers;
  - GPIO subsystem;
  - GPU drivers;
  - HID subsystem;
  - IIO subsystem;
  - IIO ADC drivers;
  - InfiniBand drivers;
  - Input Device (Miscellaneous) drivers;
  - Multiple devices driver;
  - MemoryStick subsystem;
  - MMC subsystem;
  - MTD block device drivers;
  - Network drivers;
  - Ethernet bonding driver;
  - Mellanox network drivers;
  - STMicroelectronics network drivers;
  - Ethernet team driver;
  - MediaTek network drivers;
  - NVME drivers;
  - Device tree and open firmware driver;
  - Power sequencing drivers;
  - Voltage and Current Regulator drivers;
  - Real Time Clock drivers;
  - SCSI subsystem;
  - Greybus lights staging drivers;
  - Trusted Execution Environment drivers;
  - Thunderbolt and USB4 drivers;
  - TTY drivers;
  - Cadence USB3 driver;
  - USB Device Class drivers;
  - USB core drivers;
  - DesignWare USB2 driver;
  - DesignWare USB3 driver;
  - USB Gadget drivers;
  - USB Serial drivers;
  - USB Mass Storage drivers;
  - USB Type-C suppor…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:26.04:LTS: linux, Ubuntu:26.04:LTS: linux-aws, Ubuntu:26.04:LTS: linux-gcp, Ubuntu:26.04:LTS: linux-ibm, Ubuntu:26.04:LTS: linux-oem-7.0, Ubuntu:26.04:LTS: linux-oracle&lt;/p&gt;
&lt;p&gt;Several security issues were discovered in the Linux kernel.
An attacker could possibly use these to compromise the system.
This update corrects flaws in the following subsystems:
  - Network file systems library;
  - Stream parser;
  - ARM64 architecture;
  - PowerPC architecture;
  - RISC-V architecture;
  - S390 architecture;
  - User-Mode Linux (UML);
  - x86 architecture;
  - Block layer subsystem;
  - Android drivers;
  - Bluetooth drivers;
  - TPM device driver;
  - DPLL subsystem;
  - EDAC drivers;
  - GPIO subsystem;
  - GPU drivers;
  - HID subsystem;
  - IIO subsystem;
  - IIO ADC drivers;
  - InfiniBand drivers;
  - Input Device (Miscellaneous) drivers;
  - Multiple devices driver;
  - MemoryStick subsystem;
  - MMC subsystem;
  - MTD block device drivers;
  - Network drivers;
  - Ethernet bonding driver;
  - Mellanox network drivers;
  - STMicroelectronics network drivers;
  - Ethernet team driver;
  - MediaTek network drivers;
  - NVME drivers;
  - Device tree and open firmware driver;
  - Power sequencing drivers;
  - Voltage and Current Regulator drivers;
  - Real Time Clock drivers;
  - SCSI subsystem;
  - Greybus lights staging drivers;
  - Trusted Execution Environment drivers;
  - Thunderbolt and USB4 drivers;
  - TTY drivers;
  - Cadence USB3 driver;
  - USB Device Class drivers;
  - USB core drivers;
  - DesignWare USB2 driver;
  - DesignWare USB3 driver;
  - USB Gadget drivers;
  - USB Serial drivers;
  - USB Mass Storage drivers;
  - USB Type-C suppor…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/usn-9018-1</guid>
    </item>
  </channel>
</rss>
