Out-of-bounds Write Affecting linux-6.12 package, versions <6.12.100-1~deb12u1
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk IDSNYK-ECHOLATEST-LINUX612-18579273
- published7 Aug 2026
- disclosed25 Jul 2026
Introduced: 25 Jul 2026
CVE-2026-64432 (opens in a new tab)How to fix?
Upgrade Echo:latest linux-6.12 to version 6.12.100-1~deb12u1 or higher.
NVD Description
Note: Versions mentioned in the description apply only to the upstream linux-6.12 package and not the linux-6.12 package as distributed by Echo.
See How to fix? for Echo:latest relevant fixed versions and status.
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:
- dp->lcns_follow (capacity) can be smaller than lrh->lcns_follow.
- 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").
References
- https://advisory.echohq.com/cve/CVE-2026-64432
- https://git.kernel.org/stable/c/3aa96956ca2200674e2a8f9c23ec6ecd45e5010f
- https://git.kernel.org/stable/c/57382ec6ac63b63dce2789e835fded28b698ae79
- https://git.kernel.org/stable/c/946046841013ebac8492ef49651c53638d7a9a6a
- https://git.kernel.org/stable/c/964c3fae1dfc49dde5468eace940f199cda234e9
- https://git.kernel.org/stable/c/c6f9e804f73ef809529865fbc7256dd189ff8c33
- https://git.kernel.org/stable/c/cf28fc1658463d768657cf1c27a83980d4ba7ef2
- https://git.kernel.org/stable/c/f433acc85b86f327d03ba8b03a33c105c51053de