Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2026-64600: xfs: resample the data fork mapping after cycling ILOCK

Noroxi assessment

Priority: Monitor (action score 31/100)

  • Public proof-of-concept code exists (GitHub); there is no record of exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.46% (FIRST EPSS).
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: Linux Linux 206c09b04dc5469c7ff14d8aceff2d47c88078d9, 2f4acd0fcd862e22eab45690ec2c08c80b6ef2e7, 44f891bc088958399eec27f7604928694aa35581; azl3 kernel 6.6.144.1-1 on Azure Linux 3.0 6.6.145.2-1.

Low priority for now. Upgrade to Linux Linux 206c09b04dc5469c7ff14d8aceff2d47c88078d9, 2f4acd0fcd862e22eab45690ec2c08c80b6ef2e7, 44f891bc088958399eec27f7604928694aa35581; azl3 kernel 6.6.144.1-1 on Azure Linux 3.0 6.6.145.2-1 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

HighCVSS 7.8 · v3.1—Proof of concept Fix available
Published
Jul 23, 2026
Updated
Oct 19, 2026
EPSS
0.4% · 40th percentile

Report tools

JSON

Action score

31

Monitor

Low priority for now.

CVSS
31 / 40 · 7.8 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.4%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
total

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
—
CNA · Linux
7.8
NVD has not scored this yet; the score shown is the CNA’s.

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • Proof of concept exists, no weaponized module
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2026-64600

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
linuxlinux kernel

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • linux linux kernel4.11 and later · before 5.15.212
  • linux linux kernel5.16 and later · before 6.1.178
  • linux linux kernel6.2 and later · before 6.6.145
  • linux linux kernel6.7 and later · before 6.12.96
  • linux linux kernel6.13 and later · before 6.18.39
  • linux linux kernel6.19 and later · before 7.1.4
  • linux linux kernel7.2

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 4.11affected
    • 3c68d44a2b49a0ac9165faa9c191e1e618c8a8d5 and later · before dc11be133efca5fe3a2fb02b016dee825cc12f18affected · git
    • 3c68d44a2b49a0ac9165faa9c191e1e618c8a8d5 and later · before b8c9aa832b52680ee40d6cab0efb081f9a69df05affected · git
    • 3c68d44a2b49a0ac9165faa9c191e1e618c8a8d5 and later · before 50f0012da1040f69a4e788cd9aed587c9a04983faffected · git
    • 3c68d44a2b49a0ac9165faa9c191e1e618c8a8d5 and later · before e705d81a7193dd19e69b8e2bad4696d78a4ea075affected · git
    • 3c68d44a2b49a0ac9165faa9c191e1e618c8a8d5 and later · before 206c09b04dc5469c7ff14d8aceff2d47c88078d9affected · git
    • 3c68d44a2b49a0ac9165faa9c191e1e618c8a8d5 and later · before 44f891bc088958399eec27f7604928694aa35581affected · git
    • 3c68d44a2b49a0ac9165faa9c191e1e618c8a8d5 and later · before 2f4acd0fcd862e22eab45690ec2c08c80b6ef2e7affected · git
    • before 4.11not affected · semver
    • 5.15.212 and later · up to and including 5.15.*not affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.180-16.1.180-1
Debian:12linux-6.12before 6.12.100-1~deb12u16.12.100-1~deb12u1
Debian:13linuxbefore 6.12.96-16.12.96-1
Debian:14linuxbefore 7.1.4-17.1.4-1
Red Hat:enterprise_linux_eus:10.0kernelbefore 0:6.12.0-55.89.1.el10_00:6.12.0-55.89.1.el10_0
Red Hat:enterprise_linux_eus:10.0kernel-64kbefore 0:6.12.0-55.89.1.el10_00:6.12.0-55.89.1.el10_0
Red Hat:enterprise_linux_eus:10.0kernel-64k-corebefore 0:6.12.0-55.89.1.el10_00:6.12.0-55.89.1.el10_0
Red Hat:enterprise_linux_eus:10.0kernel-64k-debugbefore 0:6.12.0-55.89.1.el10_00:6.12.0-55.89.1.el10_0
Red Hat:enterprise_linux_eus:10.0kernel-64k-debug-corebefore 0:6.12.0-55.89.1.el10_00:6.12.0-55.89.1.el10_0
Red Hat:enterprise_linux_eus:10.0kernel-64k-debug-debuginfobefore 0:6.12.0-55.89.1.el10_00:6.12.0-55.89.1.el10_0
Red Hat:enterprise_linux_eus:10.0kernel-64k-debug-develbefore 0:6.12.0-55.89.1.el10_00:6.12.0-55.89.1.el10_0
Red Hat:enterprise_linux_eus:10.0kernel-64k-debug-devel-matchedbefore 0:6.12.0-55.89.1.el10_00:6.12.0-55.89.1.el10_0
Red Hat:enterprise_linux_eus:10.0kernel-64k-debug-modulesbefore 0:6.12.0-55.89.1.el10_00:6.12.0-55.89.1.el10_0
Red Hat:enterprise_linux_eus:10.0kernel-64k-debug-modules-corebefore 0:6.12.0-55.89.1.el10_00:6.12.0-55.89.1.el10_0
Red Hat:enterprise_linux_eus:10.0kernel-64k-debug-modules-extrabefore 0:6.12.0-55.89.1.el10_00:6.12.0-55.89.1.el10_0
Red Hat:enterprise_linux_eus:10.0kernel-64k-debuginfobefore 0:6.12.0-55.89.1.el10_00:6.12.0-55.89.1.el10_0
Red Hat:enterprise_linux_eus:10.0kernel-64k-develbefore 0:6.12.0-55.89.1.el10_00:6.12.0-55.89.1.el10_0
Red Hat:enterprise_linux_eus:10.0kernel-64k-devel-matchedbefore 0:6.12.0-55.89.1.el10_00:6.12.0-55.89.1.el10_0
Red Hat:enterprise_linux_eus:10.0kernel-64k-modulesbefore 0:6.12.0-55.89.1.el10_00:6.12.0-55.89.1.el10_0
Red Hat:enterprise_linux_eus:10.0kernel-64k-modules-corebefore 0:6.12.0-55.89.1.el10_00:6.12.0-55.89.1.el10_0
Red Hat:enterprise_linux_eus:10.0kernel-64k-modules-extrabefore 0:6.12.0-55.89.1.el10_00:6.12.0-55.89.1.el10_0
Red Hat:enterprise_linux_eus:10.0kernel-abi-stablelistsbefore 0:6.12.0-55.89.1.el10_00:6.12.0-55.89.1.el10_0
Red Hat:enterprise_linux_eus:10.0kernel-corebefore 0:6.12.0-55.89.1.el10_00:6.12.0-55.89.1.el10_0
Red Hat:enterprise_linux_eus:10.0kernel-debugbefore 0:6.12.0-55.89.1.el10_00:6.12.0-55.89.1.el10_0

+96

Other highest-scoring records for the same primary product.

  • CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
    90Now
  • CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV
    89Now
  • CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
    85Now

Published before and after this one in the same product

  • ← EarlierCVE-2026-64191Jul 20, 2026 · i2c: stub: Reject I2C block transfers with invalid length
    31Monitor
  • ← EarlierCVE-2026-64206Jul 20, 2026 · Bluetooth: L2CAP: cancel pending_rx_work before taking conn->lock
    35Monitor
  • Later →CVE-2026-64208Jul 24, 2026 · crypto/krb5, rxrpc: Fix lack of pre-decrypt/pre-verify length checks
    30Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux206c09b04dc5469c7ff14d8aceff2d47c88078d9Vendor (CNA)
Linux Linux2f4acd0fcd862e22eab45690ec2c08c80b6ef2e7Vendor (CNA)
Linux Linux44f891bc088958399eec27f7604928694aa35581Vendor (CNA)
Linux Linux50f0012da1040f69a4e788cd9aed587c9a04983fVendor (CNA)
Linux Linuxb8c9aa832b52680ee40d6cab0efb081f9a69df05Vendor (CNA)
Linux Linuxdc11be133efca5fe3a2fb02b016dee825cc12f18Vendor (CNA)
Linux Linuxe705d81a7193dd19e69b8e2bad4696d78a4ea075Vendor (CNA)
azl3 kernel 6.6.144.1-1 on Azure Linux 3.06.6.145.2-1 · CBL-Mariner ReleasesMicrosoft (MSRC)
debian:linux6.1.180-1 · Debian:12Package registry (OSV)
debian:linux-6.126.12.100-1~deb12u1 · Debian:12Package registry (OSV)
red hat:kernel0:6.12.0-231.17.el10nv · Red Hat:enterprise_linux_nvidia:10::el10Package registry (OSV)
red hat:kernel-64k0:6.12.0-231.17.el10nv · Red Hat:enterprise_linux_nvidia:10::el10Package registry (OSV)
red hat:kernel-64k-core0:6.12.0-231.17.el10nv · Red Hat:enterprise_linux_nvidia:10::el10Package registry (OSV)
red hat:kernel-64k-debug0:6.12.0-231.17.el10nv · Red Hat:enterprise_linux_nvidia:10::el10Package registry (OSV)
red hat:kernel-64k-debug-core0:6.12.0-231.17.el10nv · Red Hat:enterprise_linux_nvidia:10::el10Package registry (OSV)
red hat:kernel-64k-debug-debuginfo0:6.12.0-231.17.el10nv · Red Hat:enterprise_linux_nvidia:10::el10Package registry (OSV)
red hat:kernel-64k-debug-modules0:6.12.0-231.17.el10nv · Red Hat:enterprise_linux_nvidia:10::el10Package registry (OSV)
red hat:kernel-64k-debug-modules-core0:6.12.0-231.17.el10nv · Red Hat:enterprise_linux_nvidia:10::el10Package registry (OSV)
red hat:kernel-64k-debug-modules-extra0:6.12.0-231.17.el10nv · Red Hat:enterprise_linux_nvidia:10::el10Package registry (OSV)
red hat:kernel-64k-debuginfo0:6.12.0-231.17.el10nv · Red Hat:enterprise_linux_nvidia:10::el10Package registry (OSV)
red hat:kernel-64k-modules0:6.12.0-231.17.el10nv · Red Hat:enterprise_linux_nvidia:10::el10Package registry (OSV)
red hat:kernel-64k-modules-core0:6.12.0-231.17.el10nv · Red Hat:enterprise_linux_nvidia:10::el10Package registry (OSV)
suse:kernel-livepatch-SLE16_Update_124-160000.1.1 · SUSE:Linux Micro 6.2Package registry (OSV)
suse:kernel-livepatch-SLE16_Update_134-160000.1.2 · SUSE:Linux Micro 6.2Package registry (OSV)
suse:kernel-livepatch-SLE16_Update_152-160000.1.1 · SUSE:Linux Micro 6.2Package registry (OSV)
suse:kernel-livepatch-SLE16-RT_Update_106-160000.1.1 · SUSE:Linux Micro 6.2Package registry (OSV)
suse:kernel-livepatch-SLE16-RT_Update_116-160000.1.1 · SUSE:Linux Micro 6.2Package registry (OSV)
suse:kernel-livepatch-SLE16-RT_Update_124-160000.1.1 · SUSE:Linux Micro 6.2Package registry (OSV)
suse:kernel-livepatch-SLE16-RT_Update_134-160000.1.1 · SUSE:Linux Micro 6.2Package registry (OSV)
suse:kernel-livepatch-SLE16-RT_Update_144-160000.1.1 · SUSE:Linux Micro 6.2Package registry (OSV)

+4

Exploit status

Proof of concept available

A public proof of concept or detection signature exists. Exploit knowledge is out there; don't delay patching.

Evidence

  • Proof-of-concept repository on GitHub ×10

Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.

Public exploit evidence
SourceKindDate
Proof-of-concept repository on GitHubstars:212026-07-22
Proof-of-concept repository on GitHubstars:02026-07-23
Proof-of-concept repository on GitHubstars:02026-07-24
Proof-of-concept repository on GitHubstars:72026-07-26
Proof-of-concept repository on GitHubstars:42026-07-27
Proof-of-concept repository on GitHubstars:02026-07-28
Proof-of-concept repository on GitHubstars:02026-07-28
Proof-of-concept repository on GitHubstars:12026-08-08
Proof-of-concept repository on GitHubstars:02026-08-14
Proof-of-concept repository on GitHubstars:02026-09-26

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

  1. First PoC-1 d
  2. Published
  3. TodayOct 28, 2026+97 d
EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
high · data can be read
Integrity
high · data or configuration can be modified
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
High
Availability impact
High

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

nvd-secondary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

Change log

  1. SSVC exploitation— → none
  2. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records