Linux
xfs: resample the data fork mapping after cycling ILOCK
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.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- >= 3c68d44a2b49a0ac9165faa9c191e1e618c8a8d5, < dc11be133efca5fe3a2fb02b016dee825cc12f18
- >= 3c68d44a2b49a0ac9165faa9c191e1e618c8a8d5, < b8c9aa832b52680ee40d6cab0efb081f9a69df05
- >= 3c68d44a2b49a0ac9165faa9c191e1e618c8a8d5, < 50f0012da1040f69a4e788cd9aed587c9a04983f
- >= 3c68d44a2b49a0ac9165faa9c191e1e618c8a8d5, < e705d81a7193dd19e69b8e2bad4696d78a4ea075
- >= 3c68d44a2b49a0ac9165faa9c191e1e618c8a8d5, < 206c09b04dc5469c7ff14d8aceff2d47c88078d9
- >= 3c68d44a2b49a0ac9165faa9c191e1e618c8a8d5, < 44f891bc088958399eec27f7604928694aa35581
- >= 3c68d44a2b49a0ac9165faa9c191e1e618c8a8d5, < 2f4acd0fcd862e22eab45690ec2c08c80b6ef2e7
Fixed in dc11be133efca5fe3a2fb02b016dee825cc12f18, b8c9aa832b52680ee40d6cab0efb081f9a69df05, 50f0012da1040f69a4e788cd9aed587c9a04983f, e705d81a7193dd19e69b8e2bad4696d78a4ea075, 206c09b04dc5469c7ff14d8aceff2d47c88078d9, 44f891bc088958399eec27f7604928694aa35581, 2f4acd0fcd862e22eab45690ec2c08c80b6ef2e7
- 4.11
Fixed in 0, 5.15.212, 6.1.178, 6.6.145, 6.12.96, 6.18.39, 7.1.4, 7.2
Mitigation
Upgrade Linux to dc11be133efca5fe3a2fb02b016dee825cc12f18 or b8c9aa832b52680ee40d6cab0efb081f9a69df05 or 50f0012da1040f69a4e788cd9aed587c9a04983f or e705d81a7193dd19e69b8e2bad4696d78a4ea075 or 206c09b04dc5469c7ff14d8aceff2d47c88078d9 or 44f891bc088958399eec27f7604928694aa35581 or 2f4acd0fcd862e22eab45690ec2c08c80b6ef2e7 or later.
Upgrade Linux to 0 or 5.15.212 or 6.1.178 or 6.6.145 or 6.12.96 or 6.18.39 or 7.1.4 or 7.2 or later.
Timeline
Days relative to CVE publicationFirst public PoC 9 h before publication; not in CISA KEV. First PoC: 0xBlackash/CVE-2026-64600 (created 22 Jul 2026, found by us: backfilled).
PoC repositories
Found on GitHub.10 PoCs · 1 pending · 1 suspicious or fake
PoCs 10
| Repository | Created | Stars | Assessment |
|---|---|---|---|
| 0xBlackash/CVE-2026-64600 | 22 Jul 2026 −9 h | 22 | PoC |
| 0xredash/CVE-2026-64600 | 22 Jul 2026 −9 h | 22 | PoC |
| ashrafzaryouh/CVE-2026-64600 | 22 Jul 2026 −9 h | 22 | PoC |
| HORKimhab/CVE-2026-64600 | 23 Jul 2026 +4 h | 0 | PoC via PoC Index |
| Debajyoti0-0/CVE-2026-64600 | 26 Jul 2026 +3.3 d | 7 | PoC |
| litosmartin/CVE-2026-64600-Refluxfs-PoC | 27 Jul 2026 +4 d | 4 | PoC |
| bha-vin/CVE-2026-64600-Exploit | 28 Jul 2026 +5.2 d | 0 | PoC |
| masrikky/CVE-2026-64600-RefluXFS | 8 Aug 2026 +16 d | 1 | PoC via PoC Index |
| 0xSec1/CVE-2026-64600-RefluXFS-PoC | 14 Aug 2026 +22 d | 0 | PoC |
| k4ntux/COWSlip | 26 Sep 2026 +65 d | 1 | PoC via PoC Index |
Pending 1
| Repository | Created | Stars | Assessment |
|---|---|---|---|
| vulnquest58/VQ-RefluxCore | 24 Jul 2026 +1.7 d | 0 | Pending
Flags · score 15
Below the suspicion threshold (50); does not change the assessment. |
Suspicious or fake 1
| Repository | Created | Stars | Assessment |
|---|---|---|---|
| letsr00t/RefluxFS_CVE-2026-64600 | 28 Jul 2026 +5.2 d | 0 | Fake |
Only PoCs count toward the first-PoC date and the characteristics below. Do not run PoC code from unknown sources.