CVE-2026-64532
fs/ntfs3: bound NTFS_DE view.data_off in UpdateRecordData{Root,Allocation}
Description
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" (<[email protected]>) which proposes calling ntfs3_bad_de_range(); that helper does not exist in mainline. This patch uses inline checks.
INFO
Published Date :
July 27, 2026, 8:16 a.m.
Last Modified :
July 27, 2026, 8:16 a.m.
Remotely Exploit :
No
Source :
416baaa9-dc9f-4396-8d5f-8c081fb06d67
Affected Products
The following products are affected by CVE-2026-64532
vulnerability.
Even if cvefeed.io is aware of the exact versions of the
products
that
are
affected, the information is not represented in the table below.
No affected product recoded yet
Solution
- Validate view.data_off + dlen against entry size.
- Ensure destination pointer is within bounds.
- Update the NTFS driver to the patched version.
References to Advisories, Solutions, and Tools
Here, you will find a curated list of external links that provide in-depth
information, practical solutions, and valuable tools related to
CVE-2026-64532.
CWE - Common Weakness Enumeration
While CVE identifies
specific instances of vulnerabilities, CWE categorizes the common flaws or
weaknesses that can lead to vulnerabilities. CVE-2026-64532 is
associated with the following CWEs:
Common Attack Pattern Enumeration and Classification (CAPEC)
Common Attack Pattern Enumeration and Classification
(CAPEC)
stores attack patterns, which are descriptions of the common attributes and
approaches employed by adversaries to exploit the CVE-2026-64532
weaknesses.
We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).
Results are limited to the first 15 repositories due to potential performance issues.
The following list is the news that have been mention
CVE-2026-64532 vulnerability anywhere in the article.
The following table lists the changes that have been made to the
CVE-2026-64532 vulnerability over time.
Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.
-
New CVE Received by 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Jul. 27, 2026
Action Type Old Value New Value Added Affected [{'repo': 'https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git', 'vendor': 'Linux', 'product': 'Linux', 'versions': [{'status': 'affected', 'version': 'b46acd6a6a627d876898e1c84d3f84902264b445', 'lessThan': 'b20e5a709d8bd190d6e4645606763c7423e694c1', 'versionType': 'git'}, {'status': 'affected', 'version': 'b46acd6a6a627d876898e1c84d3f84902264b445', 'lessThan': 'd41b382068ca4e64e421f736cdd700095464b6ac', 'versionType': 'git'}, {'status': 'affected', 'version': 'b46acd6a6a627d876898e1c84d3f84902264b445', 'lessThan': '429d653ca641d38a78609b8f62e81a0a5c780a2d', 'versionType': 'git'}, {'status': 'affected', 'version': 'b46acd6a6a627d876898e1c84d3f84902264b445', 'lessThan': '315d3a9a48b49f889da3d858a9307e677cb9e1bd', 'versionType': 'git'}, {'status': 'affected', 'version': 'b46acd6a6a627d876898e1c84d3f84902264b445', 'lessThan': 'be306b8d9143a9c076c804a7ca025d69caf9c448', 'versionType': 'git'}, {'status': 'affected', 'version': 'b46acd6a6a627d876898e1c84d3f84902264b445', 'lessThan': '36feda687afebae24c472202694448738809c411', 'versionType': 'git'}, {'status': 'affected', 'version': 'b46acd6a6a627d876898e1c84d3f84902264b445', 'lessThan': '3e127829e57f5190f612412ece4541cb96d5ec7a', 'versionType': 'git'}], 'programFiles': ['fs/ntfs3/fslog.c'], 'defaultStatus': 'unaffected'}, {'repo': 'https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git', 'vendor': 'Linux', 'product': 'Linux', 'versions': [{'status': 'affected', 'version': '5.15'}, {'status': 'unaffected', 'version': '0', 'lessThan': '5.15', 'versionType': 'semver'}, {'status': 'unaffected', 'version': '5.15.212', 'versionType': 'semver', 'lessThanOrEqual': '5.15.*'}, {'status': 'unaffected', 'version': '6.1.178', 'versionType': 'semver', 'lessThanOrEqual': '6.1.*'}, {'status': 'unaffected', 'version': '6.6.145', 'versionType': 'semver', 'lessThanOrEqual': '6.6.*'}, {'status': 'unaffected', 'version': '6.12.97', 'versionType': 'semver', 'lessThanOrEqual': '6.12.*'}, {'status': 'unaffected', 'version': '6.18.40', 'versionType': 'semver', 'lessThanOrEqual': '6.18.*'}, {'status': 'unaffected', 'version': '7.1.5', 'versionType': 'semver', 'lessThanOrEqual': '7.1.*'}, {'status': 'unaffected', 'version': '7.2-rc1', 'versionType': 'original_commit_for_fix', 'lessThanOrEqual': '*'}], 'programFiles': ['fs/ntfs3/fslog.c'], 'defaultStatus': 'affected'}] Added Description 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" (<[email protected]>) which proposes calling ntfs3_bad_de_range(); that helper does not exist in mainline. This patch uses inline checks. Added Reference https://git.kernel.org/stable/c/315d3a9a48b49f889da3d858a9307e677cb9e1bd Added Reference https://git.kernel.org/stable/c/36feda687afebae24c472202694448738809c411 Added Reference https://git.kernel.org/stable/c/3e127829e57f5190f612412ece4541cb96d5ec7a Added Reference https://git.kernel.org/stable/c/429d653ca641d38a78609b8f62e81a0a5c780a2d Added Reference https://git.kernel.org/stable/c/b20e5a709d8bd190d6e4645606763c7423e694c1 Added Reference https://git.kernel.org/stable/c/be306b8d9143a9c076c804a7ca025d69caf9c448 Added Reference https://git.kernel.org/stable/c/d41b382068ca4e64e421f736cdd700095464b6ac