CVE-2026-64600

In the Linux kernel, the following vulnerability has been resolved:

xfs: resample the data fork mapping after cycling ILOCK

xfs_reflink_fill_{cow_hole,delalloc} are both presented with an inode, a data fork mapping, and a cow fork mapping. Unfortunately, these two helpers cycle the ILOCK to grab a transaction, which means that the mappings are stale as soon as we reacquire the ILOCK. Currently we refresh the cow fork mapping by re-calling xfs_find_trim_cow_extent, but we dont refresh the data fork mapping beforehand, which means that the xfs_bmap_trim_cow in that function queries the refcount btree about the wrong physical blocks and returns an inaccurate value in *shared.

If *shared is now false, the directio write proceeds with a stale data fork mapping. Fix this by querying the data fork mapping if the sequence counter changes across the ILOCK cycle.

Weakness

The product contains a concurrent code sequence that requires temporary, exclusive access to a shared resource, but a timing window exists in which the shared resource can be modified by another code sequence operating concurrently.

Affected Software

Extended Description

A race condition occurs within concurrent environments, and it is effectively a property of a code sequence. Depending on the context, a code sequence may be in the form of a function call, a small number of instructions, a series of program invocations, etc. A race condition violates these properties, which are closely related:

A race condition exists when an “interfering code sequence” can still access the shared resource, violating exclusivity. The interfering code sequence could be “trusted” or “untrusted.” A trusted interfering code sequence occurs within the product; it cannot be modified by the attacker, and it can only be invoked indirectly. An untrusted interfering code sequence can be authored directly by the attacker, and typically it is external to the vulnerable product.

Potential Mitigations

• Minimize the usage of shared resources in order to remove as much complexity as possible from the control flow and to reduce the likelihood of unexpected conditions occurring.
• Additionally, this will minimize the amount of synchronization necessary and may even help to reduce the likelihood of a denial of service where an attacker may be able to repeatedly trigger a critical section (CWE-400).

Related Attack Patterns

• https://cwe.mitre.org/data/definitions/26.html
• https://cwe.mitre.org/data/definitions/29.html

References

• https://cdn2.qualys.com/advisory/2026/07/22/RefluXFS.txt
• https://git.kernel.org/stable/c/206c09b04dc5469c7ff14d8aceff2d47c88078d9
• https://git.kernel.org/stable/c/2f4acd0fcd862e22eab45690ec2c08c80b6ef2e7
• https://git.kernel.org/stable/c/44f891bc088958399eec27f7604928694aa35581
• https://git.kernel.org/stable/c/50f0012da1040f69a4e788cd9aed587c9a04983f
• https://git.kernel.org/stable/c/b8c9aa832b52680ee40d6cab0efb081f9a69df05
• https://git.kernel.org/stable/c/dc11be133efca5fe3a2fb02b016dee825cc12f18
• https://git.kernel.org/stable/c/e705d81a7193dd19e69b8e2bad4696d78a4ea075
• http://www.openwall.com/lists/oss-security/2026/07/22/14
• http://www.openwall.com/lists/oss-security/2026/07/22/18
• http://www.openwall.com/lists/oss-security/2026/07/22/19
• http://www.openwall.com/lists/oss-security/2026/07/31/3
• http://www.openwall.com/lists/oss-security/2026/08/03/4
• http://www.openwall.com/lists/oss-security/2026/08/03/8