CVE Tools
Track your stack

CVE-2026-64532

fs/ntfs3: bound NTFS_DE view.data_off in UpdateRecordData{Root,Allocation}

No known exploitation. EPSS puts it in the 3rd percentile. Fixed versions are out.

CVSS 3.17.8HighEPSS percentile3rd0.1% chance in 30 daysCISA KEVNot listedNo confirmed exploitation
No public exploit knownFix1 product4 fixed builds listed below
Check it yourself

OpenVAS · 26 checks

e.g. OID 1.3.6.1.4.1.25623.1.0.157823

Run the check

Published Updated Sources: CVE.org, NVD

NVD CVE.org

What to do

Find your product and version, then upgrade to the build on the right.

  • LinuxAffected: ≥ b46acd6a6a627d876898e1c84d3f84902264b445, < b20e5a709d8bd190d6e4645606763c7423e694c1Upgrade to: b20e5a709d8bd190d6e4645606763c7423e694c1Affected: ≥ b46acd6a6a627d876898e1c84d3f84902264b445, < d41b382068ca4e64e421f736cdd700095464b6acUpgrade to: d41b382068ca4e64e421f736cdd700095464b6acAffected: ≥ b46acd6a6a627d876898e1c84d3f84902264b445, < 429d653ca641d38a78609b8f62e81a0a5c780a2dUpgrade to: 429d653ca641d38a78609b8f62e81a0a5c780a2dAffected: ≥ b46acd6a6a627d876898e1c84d3f84902264b445, < 315d3a9a48b49f889da3d858a9307e677cb9e1bdUpgrade to: 315d3a9a48b49f889da3d858a9307e677cb9e1bd + 3 more branchesStated by: CVE record

Versions as the sources state them. Full version matrix after sign-in

Check it yourselfA free OpenVAS check exists for this CVE. Run it against your hosts.Is your organisation exposed?Request an assessment to establish which checks fit your systems.

What it is

From the CVE record

In the Linux kernel, the following vulnerability has been resolved: fs/ntfs3: bound NTFS_DE view.data_off in UpdateRecordData{Root,Allocation} In do_action()'s UpdateRecordDataRoot (fslog.c:3489) and UpdateRecordDataAllocation (fslog.c:3697) cases, the memmove destination is `Add2Ptr(e, le16_to_cpu(e->view.data_off))`, where e->view.data_off comes from an on-disk NTFS_DE inside an INDEX_ROOT or INDEX_BUFFER. Neither case validates view.data_off + dlen against e->size; the existing check_if_index_root / check_if_alloc_index helpers walk the entry chain and validate the entry's offset, but not its internal view fields. The neighbouring read sites (e.g., fs/ntfs3/index.c when iterating view entries) check view.data_off + view.data_size <= e->size. Apply the same bound at the two memmove sites. Reproduced under UML+KASAN on mainline 8d90b09e6741 via pr_warn-only probe instrumentation: with view.data_off forced to 0xFFFC, the memmove writes 32 bytes past the end of the NTFS_DE. This is similar in shape to Pavitra Jha's 2026-05-02 patch "fs/ntfs3: prevent oob in case UpdateRecordDataRoot" (<20260502105008.21827-1-jhapavitra98@gmail.com>) which proposes calling ntfs3_bad_de_range(); that helper does not exist in mainline. This patch uses inline checks.

In plain language

No plain-language summary for this CVE yet.

Exploitation

Where each signal puts this CVE on the scale from published to confirmed exploited.

EPSS3rd
CISA KEV

Not in the catalog. CISA has not confirmed exploitation.

Public exploits

No public exploit or proof of concept found in the sources we track.

EPSS

0.1% chance of exploitation activity in the next 30 days, which ranks it in the 3rd percentile of scored CVEs.

Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.

Lifecycle

10 events over 99 days, from the signal feeds we watch.

  1. Record updated
  2. Record updated
  3. Record updated
  4. Record updated
  5. OpenVAS check added
  6. Record updated

Affected products

Technical detail

CVSS 3.1 vector

Open in the CVSS calculator

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

Scored 7.8 by NVD.

How it is reached

  • Attack Vector LocalRequires local access to the vulnerable system (e.g. local login, malicious file)
  • Attack Complexity LowNo special conditions — the attack can be reliably reproduced
  • Privileges Required NoneNo authentication required — anyone can exploit this
  • User Interaction RequiredA user must click a link, open a file, or perform some action

Scope

  • Scope UnchangedImpact is limited to the vulnerable component itself

Impact if exploited

  • Confidentiality HighTotal information disclosure — all data in the component is compromised
  • Integrity HighTotal loss of integrity — attacker can modify any data in the component
  • Availability HighTotal denial of service — the component is completely unavailable

Weaknesses

ATT&CK techniques

Mapped from the weaknesses above (CWE to ATT&CK), not observed in attacks.

Sources

References in the record

And 4 more references. See all after sign-in

In the news

Watch the software you run.

My Stack ranks new CVEs for your products by real-world exploitation, so the next serious one reaches you without reading every advisory.

We'll flag the next CVE, public exploit or patch for Linux, not every advisory.