CVE-2026-64600

xfs: resample the data fork mapping after cycling ILOCK

HIGH
7.8
CVSS Score
Published: July 23, 2026 at 05:46 AM UTC
Updated: October 19, 2026 at 09:17 PM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH7.8
Exploit prediction
EPSS 0.5%
SSVC
No known exploit

Description

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

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

4.11 ≤ v < 5.15.2125.16 ≤ v < 6.1.1786.13 ≤ v < 6.18.396.19 ≤ v < 7.1.46.2 ≤ v < 6.6.1456.7 ≤ v < 6.12.963c68d44a2b49a0ac9165faa9c191e1e618c8a8d57.27.2 rc17.2 rc27.2 rc3
Vendor states this is fixed in 206c09b04dc5469c7ff14d8aceff2d47c88078d9 (fixed)
Vendor states this is fixed in 2f4acd0fcd862e22eab45690ec2c08c80b6ef2e7 (fixed)
Vendor states this is fixed in 44f891bc088958399eec27f7604928694aa35581 (fixed)
Vendor states this is fixed in 50f0012da1040f69a4e788cd9aed587c9a04983f (fixed)
Vendor states this is fixed in b8c9aa832b52680ee40d6cab0efb081f9a69df05 (fixed)
Vendor states this is fixed in dc11be133efca5fe3a2fb02b016dee825cc12f18 (fixed)
Vendor states this is fixed in e705d81a7193dd19e69b8e2bad4696d78a4ea075 (fixed)
Vendor states this is fixed in 4.11 (unaffected)
Vendor states this is fixed in 5.15.212 (unaffected)
Vendor states this is fixed in 6.1.178 (unaffected)
Vendor states this is fixed in 6.12.96 (unaffected)
Vendor states this is fixed in 6.18.39 (unaffected)
Vendor states this is fixed in 6.6.145 (unaffected)
Vendor states this is fixed in 7.1.4 (unaffected)
Vendor states this is fixed in 7.2 (unaffected)

References (14)

SSVC — Action Prioritization

SSVCNo known exploitNot automatableTotal impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

7.8HIGHLinux
Vector?

Quick Info

StatusMODIFIED
CWE
CWE-362

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card