CVE-2026-97547

xfs: fix exchange-range reflink flag clearing issue with INO1_WRITTEN

Description

In the Linux kernel, the following vulnerability has been resolved: xfs: fix exchange-range reflink flag clearing issue with INO1_WRITTEN When exchanging two full-file ranges, xmi_can_exchange_reflink_flags() can move the reflink inode flag from the file that currently has it to the other file, as long as exactly one side is marked. This assumes that the file contents, and therefore all shared extents, are exchanged. That assumption is not true when XFS_EXCHMAPS_INO1_WRITTEN is set. xfs_exchmaps_can_skip_mapping() can skip hole and unwritten mappings from file1, so an exchange can complete without moving every mapping that the earlier flag-swap decision accounted for. In that case the post-operation cleanup can clear the reflink flag from an inode that still owns shared written extents. Later writes then take the non-reflink write path and may update blocks that should still have been protected by CoW, which shows up as data corruption between reflink-related files. Fix this by disabling the reflink flag exchange whenever XFS_EXCHMAPS_INO1_WRITTEN is requested. The contents exchange can still proceed; the conservative outcome is that both inodes keep the reflink flag. The regular reflink flag cleanup path can drop the extra flag later once the inode no longer has shared extents.

Key facts

Published
25 Sep 2026
Last changed
19 Oct 2026
Assigned by
Linux
EPSS
0.2% likely to be exploited in the next 30 days, higher than 9.936% of CVEs (scores for 17 Nov 2026)

Historical context and remediation

This reference retains the original CVE publication date. A recent record update does not mean a new attack occurred.

No separately sourced impact summary is available on this page yet. Consult the description, version data and dated exploitation evidence.

No explicit remediation statement is available on this page yet. Consult the original record and vendor references before choosing a fix.

Version statuses below come from the CNA. An “unaffected” version is not necessarily a currently supported release or proof of a patch date. EPSS is a dated risk estimate, not a count of historical attacks.

Read the original CVE record.

Affected products

VendorProductVersions
LinuxLinux
  • Default status: unaffected
  • 966ceafc7a437105ecfe1cadb3747b2965a260ca up to but excluding 56f87ac2b9543be2be529b831666682e6df4bc40 (affected)
  • 966ceafc7a437105ecfe1cadb3747b2965a260ca up to but excluding fac32b9950a2aab3f8659d23b2947b8fb305c3fe (affected)
  • 966ceafc7a437105ecfe1cadb3747b2965a260ca up to but excluding 8ae30b9a8c207f9bd03a98eda7b5d641daa79bdb (affected)
  • 966ceafc7a437105ecfe1cadb3747b2965a260ca up to but excluding a23eca88448e52eb1a81549862df7adce794fafb (affected)
LinuxLinux
  • Default status: affected
  • 6.10 (affected)
  • 0 up to but excluding 6.10 (unaffected)
  • 6.12.111 up to and including 6.12.* (unaffected)
  • 6.18.53 up to and including 6.18.* (unaffected)
  • 7.2.7 up to and including 7.2.* (unaffected)
  • 7.3 up to and including * (unaffected)

Timeline

  1. 25 Sep 2026 Published

References