{"api_version":"1","generated_at":"2026-07-23T13:29:00+00:00","cve":"CVE-2026-64600","urls":{"html":"https://cve.report/CVE-2026-64600","api":"https://cve.report/api/cve/CVE-2026-64600.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2026-64600","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2026-64600"},"summary":{"title":"xfs: resample the data fork mapping after cycling ILOCK","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nxfs: resample the data fork mapping after cycling ILOCK\n\nxfs_reflink_fill_{cow_hole,delalloc} are both presented with an inode,\na data fork mapping, and a cow fork mapping.  Unfortunately, these two\nhelpers cycle the ILOCK to grab a transaction, which means that the\nmappings are stale as soon as we reacquire the ILOCK.  Currently we\nrefresh the cow fork mapping by re-calling xfs_find_trim_cow_extent, but\nwe don't refresh the data fork mapping beforehand, which means that the\nxfs_bmap_trim_cow in that function queries the refcount btree about the\nwrong physical blocks and returns an inaccurate value in *shared.\n\nIf *shared is now false, the directio write proceeds with a stale data\nfork mapping.  Fix this by querying the data fork mapping if the\nsequence counter changes across the ILOCK cycle.","state":"PUBLISHED","assigner":"Linux","published_at":"2026-07-23 06:16:50","updated_at":"2026-07-23 08:16:25"},"problem_types":[],"metrics":[],"references":[{"url":"http://www.openwall.com/lists/oss-security/2026/07/22/14","name":"http://www.openwall.com/lists/oss-security/2026/07/22/14","refsource":"af854a3a-2127-422b-91ae-364da2661108","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/2f4acd0fcd862e22eab45690ec2c08c80b6ef2e7","name":"https://git.kernel.org/stable/c/2f4acd0fcd862e22eab45690ec2c08c80b6ef2e7","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/44f891bc088958399eec27f7604928694aa35581","name":"https://git.kernel.org/stable/c/44f891bc088958399eec27f7604928694aa35581","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/e705d81a7193dd19e69b8e2bad4696d78a4ea075","name":"https://git.kernel.org/stable/c/e705d81a7193dd19e69b8e2bad4696d78a4ea075","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"http://www.openwall.com/lists/oss-security/2026/07/22/19","name":"http://www.openwall.com/lists/oss-security/2026/07/22/19","refsource":"af854a3a-2127-422b-91ae-364da2661108","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/206c09b04dc5469c7ff14d8aceff2d47c88078d9","name":"https://git.kernel.org/stable/c/206c09b04dc5469c7ff14d8aceff2d47c88078d9","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"http://www.openwall.com/lists/oss-security/2026/07/22/18","name":"http://www.openwall.com/lists/oss-security/2026/07/22/18","refsource":"af854a3a-2127-422b-91ae-364da2661108","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-64600","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-64600","name":"NVD vulnerability detail","refsource":"NVD","tags":["canonical","analysis"]}],"affected":[{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 3c68d44a2b49a0ac9165faa9c191e1e618c8a8d5 e705d81a7193dd19e69b8e2bad4696d78a4ea075 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 3c68d44a2b49a0ac9165faa9c191e1e618c8a8d5 206c09b04dc5469c7ff14d8aceff2d47c88078d9 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 3c68d44a2b49a0ac9165faa9c191e1e618c8a8d5 44f891bc088958399eec27f7604928694aa35581 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 3c68d44a2b49a0ac9165faa9c191e1e618c8a8d5 2f4acd0fcd862e22eab45690ec2c08c80b6ef2e7 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 4.11","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 4.11 semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.12.96 6.12.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.18.39 6.18.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.1.4 7.1.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.2-rc4 * original_commit_for_fix","platforms":[]}],"timeline":[],"solutions":[],"workarounds":[],"exploits":[],"credits":[],"nvd_cpes":[],"vendor_comments":[],"enrichments":{"kev":null,"epss":null,"legacy_qids":[]},"source_records":{"cve_program":{"containers":{"adp":[{"providerMetadata":{"dateUpdated":"2026-07-23T06:54:07.428Z","orgId":"af854a3a-2127-422b-91ae-364da2661108","shortName":"CVE"},"references":[{"url":"http://www.openwall.com/lists/oss-security/2026/07/22/14"},{"url":"http://www.openwall.com/lists/oss-security/2026/07/22/18"},{"url":"http://www.openwall.com/lists/oss-security/2026/07/22/19"}],"title":"CVE Program Container"}],"cna":{"affected":[{"defaultStatus":"unaffected","product":"Linux","programFiles":["fs/xfs/xfs_reflink.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"lessThan":"e705d81a7193dd19e69b8e2bad4696d78a4ea075","status":"affected","version":"3c68d44a2b49a0ac9165faa9c191e1e618c8a8d5","versionType":"git"},{"lessThan":"206c09b04dc5469c7ff14d8aceff2d47c88078d9","status":"affected","version":"3c68d44a2b49a0ac9165faa9c191e1e618c8a8d5","versionType":"git"},{"lessThan":"44f891bc088958399eec27f7604928694aa35581","status":"affected","version":"3c68d44a2b49a0ac9165faa9c191e1e618c8a8d5","versionType":"git"},{"lessThan":"2f4acd0fcd862e22eab45690ec2c08c80b6ef2e7","status":"affected","version":"3c68d44a2b49a0ac9165faa9c191e1e618c8a8d5","versionType":"git"}]},{"defaultStatus":"affected","product":"Linux","programFiles":["fs/xfs/xfs_reflink.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"status":"affected","version":"4.11"},{"lessThan":"4.11","status":"unaffected","version":"0","versionType":"semver"},{"lessThanOrEqual":"6.12.*","status":"unaffected","version":"6.12.96","versionType":"semver"},{"lessThanOrEqual":"6.18.*","status":"unaffected","version":"6.18.39","versionType":"semver"},{"lessThanOrEqual":"7.1.*","status":"unaffected","version":"7.1.4","versionType":"semver"},{"lessThanOrEqual":"*","status":"unaffected","version":"7.2-rc4","versionType":"original_commit_for_fix"}]}],"cpeApplicability":[{"nodes":[{"cpeMatch":[{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"6.12.96","versionStartIncluding":"4.11","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"6.18.39","versionStartIncluding":"4.11","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.1.4","versionStartIncluding":"4.11","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.2-rc4","versionStartIncluding":"4.11","vulnerable":true}],"negate":false,"operator":"OR"}]}],"descriptions":[{"lang":"en","value":"In the Linux kernel, the following vulnerability has been resolved:\n\nxfs: resample the data fork mapping after cycling ILOCK\n\nxfs_reflink_fill_{cow_hole,delalloc} are both presented with an inode,\na data fork mapping, and a cow fork mapping.  Unfortunately, these two\nhelpers cycle the ILOCK to grab a transaction, which means that the\nmappings are stale as soon as we reacquire the ILOCK.  Currently we\nrefresh the cow fork mapping by re-calling xfs_find_trim_cow_extent, but\nwe don't refresh the data fork mapping beforehand, which means that the\nxfs_bmap_trim_cow in that function queries the refcount btree about the\nwrong physical blocks and returns an inaccurate value in *shared.\n\nIf *shared is now false, the directio write proceeds with a stale data\nfork mapping.  Fix this by querying the data fork mapping if the\nsequence counter changes across the ILOCK cycle."}],"providerMetadata":{"dateUpdated":"2026-07-23T05:47:18.646Z","orgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","shortName":"Linux"},"references":[{"url":"https://git.kernel.org/stable/c/e705d81a7193dd19e69b8e2bad4696d78a4ea075"},{"url":"https://git.kernel.org/stable/c/206c09b04dc5469c7ff14d8aceff2d47c88078d9"},{"url":"https://git.kernel.org/stable/c/44f891bc088958399eec27f7604928694aa35581"},{"url":"https://git.kernel.org/stable/c/2f4acd0fcd862e22eab45690ec2c08c80b6ef2e7"}],"title":"xfs: resample the data fork mapping after cycling ILOCK","x_generator":{"engine":"bippy-1.2.0"}}},"cveMetadata":{"assignerOrgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","assignerShortName":"Linux","cveId":"CVE-2026-64600","datePublished":"2026-07-23T05:46:56.149Z","dateReserved":"2026-07-19T15:36:31.799Z","dateUpdated":"2026-07-23T06:54:07.428Z","state":"PUBLISHED"},"dataType":"CVE_RECORD","dataVersion":"5.2"},"nvd":{"publishedDate":"2026-07-23 06:16:50","lastModifiedDate":"2026-07-23 08:16:25","problem_types":[],"metrics":[],"configurations":[]},"legacy_mitre":{"record":{"CveYear":"2026","CveId":"64600","Ordinal":"1","Title":"xfs: resample the data fork mapping after cycling ILOCK","CVE":"CVE-2026-64600","Year":"2026"},"notes":[{"CveYear":"2026","CveId":"64600","Ordinal":"1","NoteData":"In the Linux kernel, the following vulnerability has been resolved:\n\nxfs: resample the data fork mapping after cycling ILOCK\n\nxfs_reflink_fill_{cow_hole,delalloc} are both presented with an inode,\na data fork mapping, and a cow fork mapping.  Unfortunately, these two\nhelpers cycle the ILOCK to grab a transaction, which means that the\nmappings are stale as soon as we reacquire the ILOCK.  Currently we\nrefresh the cow fork mapping by re-calling xfs_find_trim_cow_extent, but\nwe don't refresh the data fork mapping beforehand, which means that the\nxfs_bmap_trim_cow in that function queries the refcount btree about the\nwrong physical blocks and returns an inaccurate value in *shared.\n\nIf *shared is now false, the directio write proceeds with a stale data\nfork mapping.  Fix this by querying the data fork mapping if the\nsequence counter changes across the ILOCK cycle.","Type":"Description","Title":"xfs: resample the data fork mapping after cycling ILOCK"}]}}}