Skip to content
Threat Brief

← All advisories

CVE-2026-97547

Severity unknownNo known exploitationFix available

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

Record last updated

CVSS score

None

No score published yet

EPSS, chance of exploitation in 30 days

0.2%

Higher than 10% of scored CVEs. A prediction, not evidence.

CISA remediation deadline

None

Not in the KEV catalog

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.

Patching and mitigation

Patch status
Fix available (source: Microsoft MSRC)
Fix documented (source date)
Mitigation
None documented
Vendor guidance
msrc.microsoft.com (opens in a new tab)

Affected products

VendorProductAffected versionsFixed inPer
LinuxLinuxfrom 966ceafc7a437105ecfe1cadb3747b2965a260ca before 56f87ac2b9543be2be529b831666682e6df4bc4056f87ac2b9543be2be529b831666682e6df4bc40CVE Program
LinuxLinuxfrom 966ceafc7a437105ecfe1cadb3747b2965a260ca before fac32b9950a2aab3f8659d23b2947b8fb305c3fefac32b9950a2aab3f8659d23b2947b8fb305c3feCVE Program
LinuxLinuxfrom 966ceafc7a437105ecfe1cadb3747b2965a260ca before 8ae30b9a8c207f9bd03a98eda7b5d641daa79bdb8ae30b9a8c207f9bd03a98eda7b5d641daa79bdbCVE Program
LinuxLinuxfrom 966ceafc7a437105ecfe1cadb3747b2965a260ca before a23eca88448e52eb1a81549862df7adce794fafba23eca88448e52eb1a81549862df7adce794fafbCVE Program
LinuxLinux6.10Not documentedCVE Program
Microsoftazl4 kernel 6.18.50-1.5.azl4 on Azure Linux 4.0Not documented0:6.18.57-1.1.azl4Microsoft MSRC
LinuxLinux (unaffected)from 6.12.111 up to and including 6.12.*Not documentedCVE Program
LinuxLinux (unaffected)from 6.18.53 up to and including 6.18.*Not documentedCVE Program
LinuxLinux (unaffected)from 7.2.7 up to and including 7.2.*Not documentedCVE Program
LinuxLinux (unaffected)7.3Not documentedCVE Program
LinuxLinux (unaffected)all versions before 6.10Not documentedCVE Program

Timeline

  1. Disclosure

    CVE record published by Linux

    Source: CVE Program (opens in a new tab)

  2. Advisory

    Microsoft advisory published

    Source: Microsoft MSRC (opens in a new tab)

  3. Advisory change

    Microsoft advisory revised (2.0): Information published.

    Source: Microsoft MSRC (opens in a new tab)

  4. Advisory change

    Microsoft advisory revised (3.0): Information published.

    Source: Microsoft MSRC (opens in a new tab)

  5. Patch

    Fix documented by Microsoft MSRC

    Source: Microsoft MSRC (opens in a new tab)

Vendor guidance and references