CVE-2026-64600
In the Linux kernel, the following vulnerability has been resolved: …
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.
What to do now
- Check your exposureFind out whether the affected software runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Set the orderSystems that can be reached from the internet come first, then the rest.
References
- git.kernel.org/stable/c/206c09b04dc5469c7ff14d8aceff2d47c88078d9
- git.kernel.org/stable/c/2f4acd0fcd862e22eab45690ec2c08c80b6ef2e7
- git.kernel.org/stable/c/44f891bc088958399eec27f7604928694aa35581
- git.kernel.org/stable/c/e705d81a7193dd19e69b8e2bad4696d78a4ea075
- www.openwall.com/lists/oss-security/2026/07/22/14
- www.openwall.com/lists/oss-security/2026/07/22/18
- www.openwall.com/lists/oss-security/2026/07/22/19
- cdn2.qualys.com/advisory/2026/07/22/RefluXFS.txt
- nvd.nist.gov/vuln/detail/CVE-2026-64600
- cve.org/CVERecord?id=CVE-2026-64600
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.