data built 2026-10-19T13:16:53Z

Look up another CVE · open CVE-2026-64432 in the interactive tracker

CVE-2026-64432

fs/ntfs3: validate Dirty Page Table capacity in log_replay copy_lcns

7.8 EPSS 0.1% AV:L

Published 2026-07-25 (3 months ago) by the Linux kernel CNA. Subsystem fs/ntfs3. Debian urgency: not yet assigned.

What to do, per Debian release

Debian's own status for CVE-2026-64432 in every release this site tracks, and what each one means in practice. Every status below is the one the Debian Security Team publishes for this CVE. source

ReleaseStatus VersionWhat this means
Debian 12bookwormfixedDLA-4720-1 · 2026-08-05 · text6.1.180-1Update the kernel and reboot. DLA-4720-1 shipped the fix on 2026-08-05, in 6.1.180-1. A running kernel keeps the old code until the machine restarts.
Debian 13trixiefixed6.12.96-1Update the kernel and reboot. Fixed in 6.12.96-1. A running kernel keeps the old code until the machine restarts.
Debian 14forkyfixed7.1.4-1Update the kernel and reboot. Fixed in 7.1.4-1. A running kernel keeps the old code until the machine restarts.
Debian unstablesidfixed7.1.4-1Update the kernel and reboot. Fixed in 7.1.4-1. A running kernel keeps the old code until the machine restarts.
Debian 12bookworm · linux-6.12fixedDLA-4724-1 · 2026-08-07 · text6.12.100-1~deb12u1Update the kernel and reboot. DLA-4724-1 shipped the fix on 2026-08-07, in 6.12.100-1~deb12u1. A running kernel keeps the old code until the machine restarts.

The vulnerability

What the bug is

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").

Where it lives

The fix touches these files. If the subsystem is one you do not use, the practical exposure is lower, though the package is still the vulnerable one.

fs/ntfs3/fslog.c

What this is
NTFS3 FILESYSTEMMAINTAINERS section matched on fs/ntfs3/ · ntfs3@lists.linux.dev · Supported
Kernel module
ntfs3

Check it on the machine

grep -w CONFIG_NTFS3_FS /boot/config-$(uname -r)

Reads the booted kernel's own configuration, on the machine and nowhere else. =y is built in, =m is a module, and an is not set line means the code is not there.

lsmod | grep -w ntfs3

Prints a line if that module is loaded right now, and nothing if it is not. One that is not loaded can still be loaded later by anything that needs it.

Show whether Debian builds this, per release

Debian does not build this code in 3 releases. It does build it in 2 releases, so the answer depends on which release the machine runs.

  • bookwormn
  • trixiem
  • forky, sidn
  • bookworm · linux-6.12m
n
not enabled on any flavour - this release does not build the code
m
a loadable module on every flavour - check lsmod, can be blacklisted
Build switch
CONFIG_NTFS3_FS

From the configuration Debian publishes for every kernel flavour it builds. It covers only the architectures Debian ships a linux-config package for, and nothing about a kernel you built yourself. Debian's own status above stays authoritative about the source package.MAINTAINERS kbuild Makefiles Debian linux-config packages

Signals

Published
2026-07-25 (3 months ago)source
CVSS
7.8 high
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:Hsource recompute it
Attack vector
local (AV:L)source
EPSS
0.14%, higher than 2.6% of all CVEssource
CISA KEV
not listedthe KEV catalogue
Debian urgency
not yet assignedsource
Subsystem
fs/ntfs3

Upstream fixes

The versions the CNA records as introducing and fixing this, and the commit for each. source

IntroducedFixed inCommit
5.155.15.212964c3fae1dfc
5.156.1.1783aa96956ca22
5.156.6.145946046841013
5.156.12.96c6f9e804f73e
5.156.18.39cf28fc165846
5.157.1.4f433acc85b86
5.157.257382ec6ac63

Debian advisories

AdvisoryDateShipped toDebian
DLA-4724-12026-08-07bookworm 6.12.100-1~deb12u1tracker
DLA-4723-12026-08-07bullseye 6.1.180-1~deb11u1tracker
DLA-4720-12026-08-05bookworm 6.1.180-1tracker

Why the CNA scored it this way

Quoted from the kernel CNA's own scoring file, word for word. A highlighted metric carries the most severe value CVSS v3.1 defines for it, which is what pushes the score up. source

AV:LAttack vector, local
The vulnerable journal-replay code is reached by mounting a crafted local block-device or loop-backed NTFS image, not through network traffic.
AC:LAttack complexity, low
Crafted DPT and action records deterministically trigger the out-of-bounds write without a race or conditions beyond attacker control.
PR:NPrivileges required, none
Although direct mounting requires initial-namespace CAP_SYS_ADMIN, an unprivileged attacker can provide the crafted volume for a privileged victim to mount and therefore needs no privileges.
UI:RUser interaction, required
A victim must attach, select, or mount the attacker-supplied NTFS volume; replay occurs during that mount even when read-only.
S:UScope, unchanged
The corruption and resulting impacts occur within the host kernel's existing security authority, without crossing a virtualization or other scope boundary.
C:HConfidentiality impact, high
The attacker controls a sequential kernel slab out-of-bounds write that can corrupt adjacent objects and plausibly enable kernel code execution and arbitrary memory disclosure.
I:HIntegrity impact, high
The attacker-controlled 64-bit overwrite can corrupt kernel objects, pointers, or control data, making arbitrary modification and control-flow hijacking defensible.
A:HAvailability impact, high
The reproduced slab out-of-bounds write can cause an immediate kernel oops or panic, and malformed volumes can trigger it repeatedly when mounted.