Description
In the Linux kernel, the following vulnerability has been resolved:

fs/ntfs3: bound DeleteIndexEntryAllocation memmove length

In do_action()'s DeleteIndexEntryAllocation case, e->size comes
from an on-disk INDEX_BUFFER entry. When e->size makes
e + e->size point past hdr + hdr->used,
PtrOffset(e1, Add2Ptr(hdr, used)) returns a negative ptrdiff_t
that is silently cast to a quasi-infinite size_t when passed
to memmove(). The memmove then walks past the destination
buffer.

The sibling DeleteIndexEntryRoot case at fslog.c:3540-3543
already carries the corresponding guard:

if (PtrOffset(e1, Add2Ptr(hdr, used)) < esize ||
Add2Ptr(e, esize) > Add2Ptr(lrh, rec_len) ||
used + esize > le32_to_cpu(hdr->total)) {
goto dirty_vol;
}

Apply the same shape to the allocation-path case. Also reject
esize == 0: memmove(e, e, ...) is a no-op and leaves
hdr->used unchanged, hiding a malformed entry from the
existing check_index_header() walk.

Reproduced under UML+KASAN on mainline 8d90b09e6741 by
mounting a crafted NTFS image: the unguarded memmove takes a
length of 0xffffffffffffff00 and the kernel oopses in
memmove+0x81/0x1a0 on the do_action+0x36a2 frame.

[almaz.alexandrovich@paragon-software.com: clang-formatted the changes]
Published: 2026-08-15
Score: 8.4 High
EPSS: < 1% Very Low
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

The flaw resides in the Linux kernel's ntfs3 filesystem driver, where a DeleteIndexEntryAllocation operation feeds an unvalidated on‑disk size value into a memmove call. If that size is excessively large and causes a signed integer underflow when computing the destination address, the resulting memmove length becomes a huge unsigned value. The kernel then writes past the end of the buffer, triggering an oops that can lead to a kernel panic. The crash occurs when the kernel processes a crafted NTFS image, but no user‑level code execution is indicated in the report.

Affected Systems

Any Linux system that incorporates the mainline ntfs3 driver compiled into its kernel is vulnerable. This includes servers, desktop, and embedded devices running recent distributions such as Ubuntu, Debian, Fedora, RHEL/CentOS, openSUSE, and others that ship with the mainline kernel. No specific kernel version is listed, so versions built before the commit that introduced the fix are considered at risk.

Risk and Exploitability

Exploitation requires an attacker to supply a malicious NTFS image that the kernel mounts, which can be achieved by placing the image on a device the system accesses, or via remote file‑system sharing if the attacker controls the mount point. The attack is limited to users with permission to mount the filesystem. Once the malicious memmove overflow is triggered, the kernel will oops, resulting in a denial of service. The CVSS score of 8.4 indicates a high severity. The EPSS score is < 1%, indicating a very low probability of exploitation at this time, and the vulnerability is not listed in CISA KEV. The low EPSS score does not mitigate the fact that the flaw can crash any kernel instance that processes a crafted NTFS volume, so environments handling untrusted NTFS images remain at elevated risk.

Generated by OpenCVE AI on August 22, 2026 at 10:40 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Apply the latest Linux kernel update that contains the ntfs3 driver patch (e.g., kernel 6.10 or newer).
  • If a kernel update is not available, temporarily remove or blacklist the ntfs3 kernel module to prevent the vulnerable driver from loading.
  • Configure NTFS mounts to be read‑only and restricted to trusted systems, or use a user‑space NTFS reader that performs size validation before presenting data to the kernel.

Generated by OpenCVE AI on August 22, 2026 at 10:40 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Sat, 22 Aug 2026 09:30:00 +0000

Type Values Removed Values Added
Weaknesses CWE-120

Wed, 19 Aug 2026 00:15:00 +0000

Type Values Removed Values Added
Weaknesses CWE-787
References
Metrics threat_severity

None

threat_severity

Moderate


Mon, 17 Aug 2026 06:00:00 +0000

Type Values Removed Values Added
Metrics cvssV3_1

{'score': 8.4, 'vector': 'CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H'}


Sat, 15 Aug 2026 20:30:00 +0000

Type Values Removed Values Added
Weaknesses CWE-120

Sat, 15 Aug 2026 06:00:00 +0000

Type Values Removed Values Added
Description In the Linux kernel, the following vulnerability has been resolved: fs/ntfs3: bound DeleteIndexEntryAllocation memmove length In do_action()'s DeleteIndexEntryAllocation case, e->size comes from an on-disk INDEX_BUFFER entry. When e->size makes e + e->size point past hdr + hdr->used, PtrOffset(e1, Add2Ptr(hdr, used)) returns a negative ptrdiff_t that is silently cast to a quasi-infinite size_t when passed to memmove(). The memmove then walks past the destination buffer. The sibling DeleteIndexEntryRoot case at fslog.c:3540-3543 already carries the corresponding guard: if (PtrOffset(e1, Add2Ptr(hdr, used)) < esize || Add2Ptr(e, esize) > Add2Ptr(lrh, rec_len) || used + esize > le32_to_cpu(hdr->total)) { goto dirty_vol; } Apply the same shape to the allocation-path case. Also reject esize == 0: memmove(e, e, ...) is a no-op and leaves hdr->used unchanged, hiding a malformed entry from the existing check_index_header() walk. Reproduced under UML+KASAN on mainline 8d90b09e6741 by mounting a crafted NTFS image: the unguarded memmove takes a length of 0xffffffffffffff00 and the kernel oopses in memmove+0x81/0x1a0 on the do_action+0x36a2 frame. [almaz.alexandrovich@paragon-software.com: clang-formatted the changes]
Title fs/ntfs3: bound DeleteIndexEntryAllocation memmove length
First Time appeared Linux
Linux linux Kernel
CPEs cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
Vendors & Products Linux
Linux linux Kernel
References

Subscriptions

Linux Linux Kernel
cve-icon MITRE

Status: PUBLISHED

Assigner: Linux

Published:

Updated: 2026-08-17T05:41:24.114Z

Reserved: 2026-08-09T03:40:39.911Z

Link: CVE-2026-72197

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Received

Published: 2026-08-15T06:21:38.323

Modified: 2026-08-17T06:18:20.487

Link: CVE-2026-72197

cve-icon Redhat

Severity : Moderate

Publid Date: 2026-08-15T00:00:00Z

Links: CVE-2026-72197 - Bugzilla

cve-icon OpenCVE Enrichment

Updated: 2026-08-22T10:45:03Z

Weaknesses