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

fs/ntfs3: add bounds check to run_get_highest_vcn()

run_get_highest_vcn() parses a packed NTFS mapping-pairs buffer without
any length bound, relying solely on a 0x00 terminator to stop. A
crafted $LogFile UpdateMappingPairs record whose embedded attribute
contains mapping-pairs runs without a terminator causes the function to
read past the slab allocation, triggering a KASAN slab-out-of-bounds
read on mount.

The sibling function run_unpack() received an analogous bounds-check in
commit b62567bca474 ("ntfs3: add buffer boundary checks to run_unpack()"),
but run_get_highest_vcn() was missed.

Take a run_buf_size parameter and reject any run header whose payload
would extend past the buffer end, mirroring the pattern used by
run_unpack(). The caller in fslog.c passes the remaining attribute
bytes after the mapping-pairs offset.

KASAN report (on mainline v7.1 merge window HEAD):

BUG: KASAN: slab-out-of-bounds in run_get_highest_vcn+0x3c0/0x410
Read of size 1 at addr ffff88800e2d5400 by task mount/72
Call Trace:
run_get_highest_vcn+0x3c0/0x410
do_action.isra.0+0x3ba8/0x7b50
log_replay+0x9ddd/0x10200
ntfs_loadlog_and_replay+0x4ad/0x610
ntfs_fill_super+0x214a/0x4540
Published: 2026-08-15
Score: n/a
EPSS: < 1% Very Low
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

The vulnerability originates from the msfs/ntfs3 module where run_get_highest_vcn() parses a packed NTFS mapping‑pairs buffer without verifying its length, relying solely on a 0x00 terminator. A crafted $LogFile UpdateMappingPairs record that omits the terminator causes the routine to read past the slab allocation, leading to a KASAN slab‑out‑of‑bounds read on mount. The kernel crash or exposed sensitive memory can result in denial of service or potential information disclosure, but the current patch only mitigates the read rather than enabling arbitrary code execution.

Affected Systems

Any Linux system that uses the Linux kernel’s native NTFS3 driver is affected. The issue affects all kernel releases that include the unpatched ntfs3 code; no specific version range is listed, so all current and older kernels using NTFS3 remain vulnerable until the patch is applied.

Risk and Exploitability

The exploit requires the attacker to supply a malicious NTFS volume containing a specially crafted $LogFile record. The attack vector is local: the attacker must be able to create or control the NTFS volume that will be mounted. As no public exploit exists, the EPSS score is not available and the CVE is not listed in CISA’s KEV catalog. Nonetheless, the severity is significant because the bug can cause a kernel panic or reveal kernel memory, and it is triggered automatically during normal mount operations on affected volumes. Overall risk is moderate to high for environments that mount untrusted NTFS filesystems.

Generated by OpenCVE AI on August 15, 2026 at 12:16 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Update the Linux kernel to a version that includes the bounds check for run_get_highest_vcn().
  • If an immediate kernel upgrade is not possible, avoid mounting NTFS volumes that may contain a $LogFile record or mount them in read‑only mode to reduce the risk of triggering the bug.
  • Monitor system logs for KASAN out‑of‑bounds reports or kernel panics related to NTFS3 mount operations; treat any such incidents as high‑severity indicators.
  • Apply the official vendor patch or apply the commit referenced in the advisory to introduce the buffer boundary check in run_get_highest_vcn()

Generated by OpenCVE AI on August 15, 2026 at 12:16 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Sat, 15 Aug 2026 12:45:00 +0000

Type Values Removed Values Added
Weaknesses CWE-127

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: add bounds check to run_get_highest_vcn() run_get_highest_vcn() parses a packed NTFS mapping-pairs buffer without any length bound, relying solely on a 0x00 terminator to stop. A crafted $LogFile UpdateMappingPairs record whose embedded attribute contains mapping-pairs runs without a terminator causes the function to read past the slab allocation, triggering a KASAN slab-out-of-bounds read on mount. The sibling function run_unpack() received an analogous bounds-check in commit b62567bca474 ("ntfs3: add buffer boundary checks to run_unpack()"), but run_get_highest_vcn() was missed. Take a run_buf_size parameter and reject any run header whose payload would extend past the buffer end, mirroring the pattern used by run_unpack(). The caller in fslog.c passes the remaining attribute bytes after the mapping-pairs offset. KASAN report (on mainline v7.1 merge window HEAD): BUG: KASAN: slab-out-of-bounds in run_get_highest_vcn+0x3c0/0x410 Read of size 1 at addr ffff88800e2d5400 by task mount/72 Call Trace: run_get_highest_vcn+0x3c0/0x410 do_action.isra.0+0x3ba8/0x7b50 log_replay+0x9ddd/0x10200 ntfs_loadlog_and_replay+0x4ad/0x610 ntfs_fill_super+0x214a/0x4540
Title fs/ntfs3: add bounds check to run_get_highest_vcn()
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-15T05:57:17.679Z

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

Link: CVE-2026-72478

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Received

Published: 2026-08-15T06:22:21.960

Modified: 2026-08-15T06:22:21.960

Link: CVE-2026-72478

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-08-15T12:30:07Z

Weaknesses