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 don't 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.

CVSS 3.1

7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

EPSS

0.5% chance of exploitation in the next 30 days; higher than 40% of CVEs (scores of 2026-10-25)

CWE

CWE-362

Published

2026-07-23

Modified

2026-10-19

Record from

the NVD, synced 2026-10-21

Affected

• linux:linux_kernel

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

Check your stackJSON