CVE-2026-64600

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.

Severity
HIGH
CVSS v3
7.8
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H · source cna
Exploit chance (EPSS)
0.467%
chance of exploitation in the next 30 days
higher than 41% of scored CVEs · 2026-11-17
CISA KEV
Not listed
Public exploit code
Yes
Exploit references (NVD and CNA): 2
Metasploit modules: 0
Nuclei templates: 0

Weakness

CISA SSVC decision points

Exploitationnone
Automatableno
Technical impacttotal
Scored2026-10-16

Timeline

  1. 2026-07-23Published by the CNA05:46 UTC
  2. 2026-10-16CISA SSVC decision recorded85 days after publication

The timeline shows what already happened. To be told when this CVE changes next, watch it from the API.

Affected products

Products listed as vulnerable. Upgrade to the version under "Fixed in", or a later one.

ProductVulnerable versionsFixed in
linux linux_kernelfrom 4.11 before 5.15.212fixed in 5.15.212from 4.11 before 6.1.178fixed in 6.1.178from 5.16 before 6.1.178fixed in 6.1.178from 4.11 before 6.12.96fixed in 6.12.96from 6.7 before 6.12.96fixed in 6.12.96(+8 more)5.15.2126.1.1786.1.1786.12.966.12.96

Products and versions as NVD and the vendor that published the CVE list them.

References

Get more CVE data from the API.

Free without a key or signup. Pro adds monitoring and higher limits: pricing.

Sources