Vulnerability · Published Oct 23, 2026 · Assigned by Linux

CVE-2026-98975xfs: stop exchanging reflink flags when exchanging mappings

High 7.8

In plain English

A high-severity security flaw in Linux from Linux. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 0.2% (higher than 6% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.

Severity (CVSS 3.1)7.8High
Exploit odds (30 days)0.2%top 94.4% of all CVEs
Exploited in the wildNo reportsnot in CISA KEV
Attack toolingNoneno public tooling known

Official description

In the Linux kernel, the following vulnerability has been resolved: xfs: stop exchanging reflink flags when exchanging mappings When an exchange covers both files from offset 0 to i_disk_size, xmi_can_exchange_reflink_flags() assumes every mapping moved and hands the reflink flag over to the other file. That assumption is wrong. A file can still own shared blocks past i_disk_size, e.g. after EXCHANGE_RANGE_TO_EOF sets a smaller size without unmapping anything. The flag is cleared anyway, and the next write to such a block happens in place instead of CoW, corrupting the other file that shares it. Commit a23eca88448e ("xfs: fix exchange-range reflink flag clearing issue with INO1_WRITTEN") fixed one instance of this. Rather than add another special case, stop moving the flags. xfs_exchmaps_ensure_reflink() already sets the flag on both inodes before the exchange, so both just keep it. Nothing sets CLEAR_INO{1,2}_REFLINK anymore. Intents logged by older kernels may still carry them; recovery already masks them off, so they stay in the log format mask and are ignored. XFS_IOC_SWAPEXT has the same problem: it moves the reflink flag from one inode to the other along with the extents. Just removing that is not enough here: the exchange path flags both inodes up front in xfs_exchmaps_ensure_reflink(), but swapext has no such step, so the inode receiving the shared extents would be left without the flag. Set it on both inodes instead, and make sure both have a CoW fork, since an inode with the reflink flag is expected to have one. The flag now stays until FALLOC_FL_UNSHARE_RANGE, xfs_scrub, or a truncate to zero removes it.

Affected packages & fixed versions

EcosystemPackageFixed inAdvisory
Debian:12linuxno fix listedDEBIAN-CVE-2026-98975
Debian:13linux6.12.115-2DEBIAN-CVE-2026-98975
Debian:14linux7.2.11-1DEBIAN-CVE-2026-98975
Ubuntu:22.04:LTSlinuxno fix listedUBUNTU-CVE-2026-98975
Ubuntu:24.04:LTSlinuxno fix listedUBUNTU-CVE-2026-98975
Ubuntu:26.04:LTSlinuxno fix listedUBUNTU-CVE-2026-98975
Ubuntu:26.10linux7.3.0-10.10UBUNTU-CVE-2026-98975
Ubuntu:22.04:LTSlinux-allwinner-5.19no fix listedUBUNTU-CVE-2026-98975
Ubuntu:22.04:LTSlinux-awsno fix listedUBUNTU-CVE-2026-98975
Ubuntu:24.04:LTSlinux-awsno fix listedUBUNTU-CVE-2026-98975
Ubuntu:26.04:LTSlinux-awsno fix listedUBUNTU-CVE-2026-98975
Ubuntu:26.10linux-aws7.3.0-1004.4UBUNTU-CVE-2026-98975
Ubuntu:22.04:LTSlinux-aws-5.19no fix listedUBUNTU-CVE-2026-98975
Ubuntu:24.04:LTSlinux-aws-6.14no fix listedUBUNTU-CVE-2026-98975
Ubuntu:24.04:LTSlinux-aws-6.17no fix listedUBUNTU-CVE-2026-98975
Ubuntu:22.04:LTSlinux-aws-6.2no fix listedUBUNTU-CVE-2026-98975
Ubuntu:22.04:LTSlinux-aws-6.5no fix listedUBUNTU-CVE-2026-98975
Ubuntu:22.04:LTSlinux-aws-6.8no fix listedUBUNTU-CVE-2026-98975
Ubuntu:24.04:LTSlinux-aws-7.0no fix listedUBUNTU-CVE-2026-98975
Ubuntu:22.04:LTSlinux-azureno fix listedUBUNTU-CVE-2026-98975
Ubuntu:24.04:LTSlinux-azureno fix listedUBUNTU-CVE-2026-98975
Ubuntu:26.04:LTSlinux-azureno fix listedUBUNTU-CVE-2026-98975
Ubuntu:26.10linux-azureno fix listedUBUNTU-CVE-2026-98975
Ubuntu:22.04:LTSlinux-azure-5.19no fix listedUBUNTU-CVE-2026-98975
Ubuntu:24.04:LTSlinux-azure-6.11no fix listedUBUNTU-CVE-2026-98975
Ubuntu:24.04:LTSlinux-azure-6.14no fix listedUBUNTU-CVE-2026-98975
Ubuntu:24.04:LTSlinux-azure-6.17no fix listedUBUNTU-CVE-2026-98975
Ubuntu:22.04:LTSlinux-azure-6.2no fix listedUBUNTU-CVE-2026-98975
Ubuntu:22.04:LTSlinux-azure-6.5no fix listedUBUNTU-CVE-2026-98975
Ubuntu:22.04:LTSlinux-azure-6.8no fix listedUBUNTU-CVE-2026-98975
Ubuntu:24.04:LTSlinux-azure-7.0no fix listedUBUNTU-CVE-2026-98975
Ubuntu:22.04:LTSlinux-azure-fdeno fix listedUBUNTU-CVE-2026-98975
Ubuntu:24.04:LTSlinux-azure-fdeno fix listedUBUNTU-CVE-2026-98975
Ubuntu:26.04:LTSlinux-azure-fdeno fix listedUBUNTU-CVE-2026-98975
Ubuntu:26.10linux-azure-fdeno fix listedUBUNTU-CVE-2026-98975
Ubuntu:22.04:LTSlinux-azure-fde-5.19no fix listedUBUNTU-CVE-2026-98975
Ubuntu:24.04:LTSlinux-azure-fde-6.14no fix listedUBUNTU-CVE-2026-98975
Ubuntu:24.04:LTSlinux-azure-fde-6.17no fix listedUBUNTU-CVE-2026-98975
Ubuntu:22.04:LTSlinux-azure-fde-6.2no fix listedUBUNTU-CVE-2026-98975
Ubuntu:22.04:LTSlinux-azure-fde-6.8no fix listedUBUNTU-CVE-2026-98975
Ubuntu:24.04:LTSlinux-azure-fde-7.0no fix listedUBUNTU-CVE-2026-98975
Ubuntu:24.04:LTSlinux-azure-nvidiano fix listedUBUNTU-CVE-2026-98975
Ubuntu:24.04:LTSlinux-azure-nvidia-6.14no fix listedUBUNTU-CVE-2026-98975
Ubuntu:22.04:LTSlinux-gcpno fix listedUBUNTU-CVE-2026-98975
Ubuntu:24.04:LTSlinux-gcpno fix listedUBUNTU-CVE-2026-98975
Ubuntu:26.04:LTSlinux-gcpno fix listedUBUNTU-CVE-2026-98975
Ubuntu:26.10linux-gcp7.3.0-1004.4UBUNTU-CVE-2026-98975
Ubuntu:22.04:LTSlinux-gcp-5.19no fix listedUBUNTU-CVE-2026-98975
Ubuntu:24.04:LTSlinux-gcp-6.11no fix listedUBUNTU-CVE-2026-98975
Ubuntu:24.04:LTSlinux-gcp-6.14no fix listedUBUNTU-CVE-2026-98975
Ubuntu:24.04:LTSlinux-gcp-6.17no fix listedUBUNTU-CVE-2026-98975
Ubuntu:22.04:LTSlinux-gcp-6.2no fix listedUBUNTU-CVE-2026-98975
Ubuntu:22.04:LTSlinux-gcp-6.5no fix listedUBUNTU-CVE-2026-98975
Ubuntu:22.04:LTSlinux-gcp-6.8no fix listedUBUNTU-CVE-2026-98975
Ubuntu:24.04:LTSlinux-gcp-7.0no fix listedUBUNTU-CVE-2026-98975
Ubuntu:22.04:LTSlinux-gkeno fix listedUBUNTU-CVE-2026-98975
Ubuntu:24.04:LTSlinux-gkeno fix listedUBUNTU-CVE-2026-98975
Ubuntu:26.04:LTSlinux-gkeno fix listedUBUNTU-CVE-2026-98975
Ubuntu:22.04:LTSlinux-gkeopno fix listedUBUNTU-CVE-2026-98975
Ubuntu:24.04:LTSlinux-gkeopno fix listedUBUNTU-CVE-2026-98975
Ubuntu:22.04:LTSlinux-hwe-5.19no fix listedUBUNTU-CVE-2026-98975
Ubuntu:24.04:LTSlinux-hwe-6.11no fix listedUBUNTU-CVE-2026-98975
Ubuntu:24.04:LTSlinux-hwe-6.14no fix listedUBUNTU-CVE-2026-98975
Ubuntu:24.04:LTSlinux-hwe-6.17no fix listedUBUNTU-CVE-2026-98975
Ubuntu:22.04:LTSlinux-hwe-6.2no fix listedUBUNTU-CVE-2026-98975
Ubuntu:22.04:LTSlinux-hwe-6.5no fix listedUBUNTU-CVE-2026-98975
Ubuntu:22.04:LTSlinux-hwe-6.8no fix listedUBUNTU-CVE-2026-98975
Ubuntu:24.04:LTSlinux-hwe-7.0no fix listedUBUNTU-CVE-2026-98975
Ubuntu:22.04:LTSlinux-ibmno fix listedUBUNTU-CVE-2026-98975
Ubuntu:24.04:LTSlinux-ibmno fix listedUBUNTU-CVE-2026-98975
Ubuntu:26.04:LTSlinux-ibmno fix listedUBUNTU-CVE-2026-98975
Ubuntu:22.04:LTSlinux-ibm-6.8no fix listedUBUNTU-CVE-2026-98975
Ubuntu:22.04:LTSlinux-intel-iot-realtimeno fix listedUBUNTU-CVE-2026-98975
Ubuntu:22.04:LTSlinux-intel-iotgno fix listedUBUNTU-CVE-2026-98975
Ubuntu:22.04:LTSlinux-kvmno fix listedUBUNTU-CVE-2026-98975
Ubuntu:22.04:LTSlinux-lowlatencyno fix listedUBUNTU-CVE-2026-98975
Ubuntu:24.04:LTSlinux-lowlatencyno fix listedUBUNTU-CVE-2026-98975
Ubuntu:22.04:LTSlinux-lowlatency-hwe-5.19no fix listedUBUNTU-CVE-2026-98975
Ubuntu:24.04:LTSlinux-lowlatency-hwe-6.11no fix listedUBUNTU-CVE-2026-98975
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.2no fix listedUBUNTU-CVE-2026-98975
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.5no fix listedUBUNTU-CVE-2026-98975
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.8no fix listedUBUNTU-CVE-2026-98975
Ubuntu:22.04:LTSlinux-nvidiano fix listedUBUNTU-CVE-2026-98975
Ubuntu:24.04:LTSlinux-nvidiano fix listedUBUNTU-CVE-2026-98975
Ubuntu:26.04:LTSlinux-nvidiano fix listedUBUNTU-CVE-2026-98975
Ubuntu:24.04:LTSlinux-nvidia-6.11no fix listedUBUNTU-CVE-2026-98975
Ubuntu:24.04:LTSlinux-nvidia-6.17no fix listedUBUNTU-CVE-2026-98975
Ubuntu:22.04:LTSlinux-nvidia-6.2no fix listedUBUNTU-CVE-2026-98975
Ubuntu:22.04:LTSlinux-nvidia-6.5no fix listedUBUNTU-CVE-2026-98975
Ubuntu:22.04:LTSlinux-nvidia-6.8no fix listedUBUNTU-CVE-2026-98975
Ubuntu:24.04:LTSlinux-nvidia-7.0no fix listedUBUNTU-CVE-2026-98975
Ubuntu:26.04:LTSlinux-nvidia-bosno fix listedUBUNTU-CVE-2026-98975
Ubuntu:24.04:LTSlinux-nvidia-lowlatencyno fix listedUBUNTU-CVE-2026-98975
Ubuntu:22.04:LTSlinux-nvidia-tegrano fix listedUBUNTU-CVE-2026-98975
Ubuntu:24.04:LTSlinux-nvidia-tegrano fix listedUBUNTU-CVE-2026-98975
Ubuntu:22.04:LTSlinux-nvidia-tegra-igxno fix listedUBUNTU-CVE-2026-98975
Ubuntu:22.04:LTSlinux-oem-5.17no fix listedUBUNTU-CVE-2026-98975
Ubuntu:22.04:LTSlinux-oem-6.0no fix listedUBUNTU-CVE-2026-98975
Ubuntu:22.04:LTSlinux-oem-6.1no fix listedUBUNTU-CVE-2026-98975
Ubuntu:24.04:LTSlinux-oem-6.11no fix listedUBUNTU-CVE-2026-98975
Ubuntu:24.04:LTSlinux-oem-6.14no fix listedUBUNTU-CVE-2026-98975
Ubuntu:24.04:LTSlinux-oem-6.17no fix listedUBUNTU-CVE-2026-98975
Ubuntu:22.04:LTSlinux-oem-6.5no fix listedUBUNTU-CVE-2026-98975
Ubuntu:24.04:LTSlinux-oem-6.8no fix listedUBUNTU-CVE-2026-98975
Ubuntu:26.04:LTSlinux-oem-7.0no fix listedUBUNTU-CVE-2026-98975
Ubuntu:22.04:LTSlinux-oracleno fix listedUBUNTU-CVE-2026-98975
Ubuntu:24.04:LTSlinux-oracleno fix listedUBUNTU-CVE-2026-98975
Ubuntu:26.04:LTSlinux-oracleno fix listedUBUNTU-CVE-2026-98975
Ubuntu:26.10linux-oracle7.3.0-1004.4UBUNTU-CVE-2026-98975
Ubuntu:24.04:LTSlinux-oracle-6.14no fix listedUBUNTU-CVE-2026-98975
Ubuntu:24.04:LTSlinux-oracle-6.17no fix listedUBUNTU-CVE-2026-98975
Ubuntu:22.04:LTSlinux-oracle-6.5no fix listedUBUNTU-CVE-2026-98975
Ubuntu:22.04:LTSlinux-oracle-6.8no fix listedUBUNTU-CVE-2026-98975
Ubuntu:24.04:LTSlinux-oracle-7.0no fix listedUBUNTU-CVE-2026-98975
Ubuntu:22.04:LTSlinux-raspino fix listedUBUNTU-CVE-2026-98975
Ubuntu:24.04:LTSlinux-raspino fix listedUBUNTU-CVE-2026-98975
Ubuntu:26.04:LTSlinux-raspino fix listedUBUNTU-CVE-2026-98975
Ubuntu:26.10linux-raspi7.3.0-1004.4UBUNTU-CVE-2026-98975
Ubuntu:24.04:LTSlinux-raspi-realtimeno fix listedUBUNTU-CVE-2026-98975
Ubuntu:22.04:LTSlinux-realtimeno fix listedUBUNTU-CVE-2026-98975
Ubuntu:24.04:LTSlinux-realtimeno fix listedUBUNTU-CVE-2026-98975
Ubuntu:26.04:LTSlinux-realtimeno fix listedUBUNTU-CVE-2026-98975
Ubuntu:26.10linux-realtime7.3.0-10.10.1UBUNTU-CVE-2026-98975
Ubuntu:22.04:LTSlinux-riscvno fix listedUBUNTU-CVE-2026-98975
Ubuntu:24.04:LTSlinux-riscvno fix listedUBUNTU-CVE-2026-98975
Ubuntu:26.04:LTSlinux-riscvno fix listedUBUNTU-CVE-2026-98975
Ubuntu:26.10linux-riscv7.3.0-10.10.1UBUNTU-CVE-2026-98975
Ubuntu:22.04:LTSlinux-riscv-5.19no fix listedUBUNTU-CVE-2026-98975
Ubuntu:24.04:LTSlinux-riscv-6.14no fix listedUBUNTU-CVE-2026-98975
Ubuntu:24.04:LTSlinux-riscv-6.17no fix listedUBUNTU-CVE-2026-98975
Ubuntu:22.04:LTSlinux-riscv-6.5no fix listedUBUNTU-CVE-2026-98975
Ubuntu:22.04:LTSlinux-riscv-6.8no fix listedUBUNTU-CVE-2026-98975
Ubuntu:24.04:LTSlinux-riscv-7.0no fix listedUBUNTU-CVE-2026-98975
Ubuntu:22.04:LTSlinux-starfive-5.19no fix listedUBUNTU-CVE-2026-98975
Ubuntu:22.04:LTSlinux-starfive-6.2no fix listedUBUNTU-CVE-2026-98975
Ubuntu:22.04:LTSlinux-starfive-6.5no fix listedUBUNTU-CVE-2026-98975
Ubuntu:24.04:LTSlinux-vmwareno fix listedUBUNTU-CVE-2026-98975
Ubuntu:24.04:LTSlinux-xilinxno fix listedUBUNTU-CVE-2026-98975
Ubuntu:22.04:LTSlinux-xilinx-zynqmpno fix listedUBUNTU-CVE-2026-98975

Affected products (as reported)

VendorProductVersions
Linux Linux f0bc4d134b46607967bda1205ce3226a1bd95f42 – before 1fa2f3a7ef7ee0f2503a4b0afe24bc8c9d0820bef0bc4d134b46607967bda1205ce3226a1bd95f42 – before 7d3b9b2c9dc57f93f36c716ab752548cb4db9900f0bc4d134b46607967bda1205ce3226a1bd95f42 – before 4756c94260e69ce42612b8220c3614f02f7a11d5f0bc4d134b46607967bda1205ce3226a1bd95f42 – before d84d6c1a7f1e2de9e601703a326a4c1b7b421943
Linux Linux 4.9

References