Answer in brief
CVE-2026-64600 records a High severity (CVSS 7.8) vulnerability in xfs: resample the data fork mapping after cycling ILOCK. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
Answer in brief
CVE-2026-64600 records a High severity (CVSS 7.8) vulnerability in xfs: resample the data fork mapping after cycling ILOCK. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 7.8. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=3c68d44a2b49a0ac9165faa9c191e1e618c8a8d5 <dc11be133efca5fe3a2fb02b016dee825cc12f18 || >=3c68d44a2b49a0ac9165faa9c191e1e618c8a8d5 <b8c9aa832b52680ee40d6cab0efb081f9a69df05 || >=3c68d44a2b49a0ac9165faa9c191e1e618c8a8d5 <50f0012da1040f69a4e788cd9aed587c9a04983f || >=3c68d44a2b49a0ac9165faa9c191e1e618c8a8d5 <e705d81a7193dd19e69b8e2bad4696d78a4ea075 || >=3c68d44a2b49a0ac9165faa9c191e1e618c8a8d5 <206c09b04dc5469c7ff14d8aceff2d47c88078d9 || >=3c68d44a2b49a0ac9165faa9c191e1e618c8a8d5 <44f891bc088958399eec27f7604928694aa35581 || >=3c68d44a2b49a0ac9165faa9c191e1e618c8a8d5 <2f4acd0fcd862e22eab45690ec2c08c80b6ef2e7 | dc11be133efca5fe3a2fb02b016dee825cc12f18, b8c9aa832b52680ee40d6cab0efb081f9a69df05, 50f0012da1040f69a4e788cd9aed587c9a04983f, e705d81a7193dd19e69b8e2bad4696d78a4ea075, 206c09b04dc5469c7ff14d8aceff2d47c88078d9, 44f891bc088958399eec27f7604928694aa35581, 2f4acd0fcd862e22eab45690ec2c08c80b6ef2e7 |
| Linux/Linuxgeneric | 4.11 | Not reported |
Published upstream
Jul 23, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 3, 2026
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.
Quoted source text, attributed separately from HOL analysis.
CVSS is 7.8. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=3c68d44a2b49a0ac9165faa9c191e1e618c8a8d5 <dc11be133efca5fe3a2fb02b016dee825cc12f18 || >=3c68d44a2b49a0ac9165faa9c191e1e618c8a8d5 <b8c9aa832b52680ee40d6cab0efb081f9a69df05 || >=3c68d44a2b49a0ac9165faa9c191e1e618c8a8d5 <50f0012da1040f69a4e788cd9aed587c9a04983f || >=3c68d44a2b49a0ac9165faa9c191e1e618c8a8d5 <e705d81a7193dd19e69b8e2bad4696d78a4ea075 || >=3c68d44a2b49a0ac9165faa9c191e1e618c8a8d5 <206c09b04dc5469c7ff14d8aceff2d47c88078d9 || >=3c68d44a2b49a0ac9165faa9c191e1e618c8a8d5 <44f891bc088958399eec27f7604928694aa35581 || >=3c68d44a2b49a0ac9165faa9c191e1e618c8a8d5 <2f4acd0fcd862e22eab45690ec2c08c80b6ef2e7 | dc11be133efca5fe3a2fb02b016dee825cc12f18, b8c9aa832b52680ee40d6cab0efb081f9a69df05, 50f0012da1040f69a4e788cd9aed587c9a04983f, e705d81a7193dd19e69b8e2bad4696d78a4ea075, 206c09b04dc5469c7ff14d8aceff2d47c88078d9, 44f891bc088958399eec27f7604928694aa35581, 2f4acd0fcd862e22eab45690ec2c08c80b6ef2e7 |
| Linux/Linuxgeneric | 4.11 | Not reported |
Published upstream
Jul 23, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 3, 2026
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.
Quoted source text, attributed separately from HOL analysis.