CVE-2026-64432
fs/ntfs3: validate Dirty Page Table capacity in log_replay copy_lcns
Description
In the Linux kernel, the following vulnerability has been resolved: fs/ntfs3: validate Dirty Page Table capacity in log_replay copy_lcns In the analysis pass of $LogFile journal replay, log_replay() copies LCNs from each action log record into an existing Dirty Page Table (DPT) entry without bounding the destination index. A crafted NTFS image with DPT entry lcns_follow=1 and an action log record with lcns_follow=2 produces a kernel slab out-of-bounds write at mount time: BUG: KASAN: slab-out-of-bounds in log_replay+0x654c/0xdb60 Write of size 8 at addr ffff8880095e1040 by task mount Two attacker-controlled fields can drive j+i past the allocated page_lcns[] array: 1. dp->lcns_follow (capacity) can be smaller than lrh->lcns_follow. 2. lrh->target_vcn may be smaller than dp->vcn, making the u64 subtraction wrap to a huge size_t. Validate target VCN delta and per-record LCN count against the DPT entry capacity, bail via the existing out: cleanup label with -EINVAL. This mirrors the bounds-check pattern added in commit b2bc7c44ed17 ("fs/ntfs3: Fix slab-out-of-bounds read in DeleteIndexEntryRoot") and commit 0ca0485e4b2e ("fs/ntfs3: validate rec->used in journal-replay file record check").
INFO
Published Date :
July 25, 2026, 10:17 a.m.
Last Modified :
July 25, 2026, 10:17 a.m.
Remotely Exploit :
No
Source :
416baaa9-dc9f-4396-8d5f-8c081fb06d67
Affected Products
The following products are affected by CVE-2026-64432
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 target VCN delta against DPT capacity.
- Validate per-record LCN count against DPT capacity.
- Bail with -EINVAL if validation fails.
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-64432.
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-64432 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-64432
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-64432 vulnerability anywhere in the article.
The following table lists the changes that have been made to the
CVE-2026-64432 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. 25, 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': '964c3fae1dfc49dde5468eace940f199cda234e9', 'versionType': 'git'}, {'status': 'affected', 'version': 'b46acd6a6a627d876898e1c84d3f84902264b445', 'lessThan': '3aa96956ca2200674e2a8f9c23ec6ecd45e5010f', 'versionType': 'git'}, {'status': 'affected', 'version': 'b46acd6a6a627d876898e1c84d3f84902264b445', 'lessThan': '946046841013ebac8492ef49651c53638d7a9a6a', 'versionType': 'git'}, {'status': 'affected', 'version': 'b46acd6a6a627d876898e1c84d3f84902264b445', 'lessThan': 'c6f9e804f73ef809529865fbc7256dd189ff8c33', 'versionType': 'git'}, {'status': 'affected', 'version': 'b46acd6a6a627d876898e1c84d3f84902264b445', 'lessThan': 'cf28fc1658463d768657cf1c27a83980d4ba7ef2', 'versionType': 'git'}, {'status': 'affected', 'version': 'b46acd6a6a627d876898e1c84d3f84902264b445', 'lessThan': 'f433acc85b86f327d03ba8b03a33c105c51053de', 'versionType': 'git'}, {'status': 'affected', 'version': 'b46acd6a6a627d876898e1c84d3f84902264b445', 'lessThan': '57382ec6ac63b63dce2789e835fded28b698ae79', '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.96', 'versionType': 'semver', 'lessThanOrEqual': '6.12.*'}, {'status': 'unaffected', 'version': '6.18.39', 'versionType': 'semver', 'lessThanOrEqual': '6.18.*'}, {'status': 'unaffected', 'version': '7.1.4', '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: validate Dirty Page Table capacity in log_replay copy_lcns In the analysis pass of $LogFile journal replay, log_replay() copies LCNs from each action log record into an existing Dirty Page Table (DPT) entry without bounding the destination index. A crafted NTFS image with DPT entry lcns_follow=1 and an action log record with lcns_follow=2 produces a kernel slab out-of-bounds write at mount time: BUG: KASAN: slab-out-of-bounds in log_replay+0x654c/0xdb60 Write of size 8 at addr ffff8880095e1040 by task mount Two attacker-controlled fields can drive j+i past the allocated page_lcns[] array: 1. dp->lcns_follow (capacity) can be smaller than lrh->lcns_follow. 2. lrh->target_vcn may be smaller than dp->vcn, making the u64 subtraction wrap to a huge size_t. Validate target VCN delta and per-record LCN count against the DPT entry capacity, bail via the existing out: cleanup label with -EINVAL. This mirrors the bounds-check pattern added in commit b2bc7c44ed17 ("fs/ntfs3: Fix slab-out-of-bounds read in DeleteIndexEntryRoot") and commit 0ca0485e4b2e ("fs/ntfs3: validate rec->used in journal-replay file record check"). Added Reference https://git.kernel.org/stable/c/3aa96956ca2200674e2a8f9c23ec6ecd45e5010f Added Reference https://git.kernel.org/stable/c/57382ec6ac63b63dce2789e835fded28b698ae79 Added Reference https://git.kernel.org/stable/c/946046841013ebac8492ef49651c53638d7a9a6a Added Reference https://git.kernel.org/stable/c/964c3fae1dfc49dde5468eace940f199cda234e9 Added Reference https://git.kernel.org/stable/c/c6f9e804f73ef809529865fbc7256dd189ff8c33 Added Reference https://git.kernel.org/stable/c/cf28fc1658463d768657cf1c27a83980d4ba7ef2 Added Reference https://git.kernel.org/stable/c/f433acc85b86f327d03ba8b03a33c105c51053de