LiveActive security incident?Get immediate response
CVE Record

CVE-2026-46072: ntfs3: add buffer boundary checks to run_unpack()

In the Linux kernel, the following vulnerability has been resolved: ntfs3: add buffer boundary checks to run_unpack() run_unpack() checks `run_buf < run_last` at the top of the while loop but then reads size_size and offset_size bytes via run_unpack_s64() without verifying they fit within the remaining buffer. A crafted NTFS image with truncated run data in an MFT attribute triggers an OOB heap read of up to 15 bytes when the filesystem is mounted. Add boundary checks before each run_unpack_s64() call to ensure the declared field size does not exceed the remaining buffer. Found by fuzzing with a source-patched harness (LibAFL + QEMU).

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This is a Linux kernel NTFS driver flaw. A specially crafted NTFS filesystem image can make the kernel read past a heap buffer when the image is mounted. The source describes a small out-of-bounds read, not code execution, and gives no evidence of active exploitation.

Executive priority

Treat this as a targeted kernel-hardening update, not an emergency internet-facing incident. Prioritize systems likely to mount untrusted NTFS media or images. The absence of CVSS and exploitation evidence lowers urgency, but kernel parsing bugs still deserve timely patching.

Technical view

The ntfs3 run_unpack() parser checked the loop boundary but did not verify declared size and offset fields before run_unpack_s64() reads. Truncated run data in an MFT attribute can trigger an out-of-bounds heap read of up to 15 bytes during mount. Stable kernel commits add remaining-buffer checks before those reads.

Likely exposure

Exposure is most relevant to Linux systems that mount NTFS filesystems using ntfs3, especially desktops, forensic workstations, file-ingest systems, virtualization hosts, and servers that handle removable media or user-supplied disk images. Distro-specific affected package status is not provided in the source bundle.

Exploitation context

The provided sources do not show KEV listing or active exploitation. The described trigger requires a crafted NTFS image and a mount operation. The issue was found by fuzzing with a LibAFL and QEMU harness, which supports reproducibility but not real-world exploitation evidence.

Researcher notes

Evidence is limited to the CVE description and Linux stable commit references. The affected version data is not distro-normalized, and no CVSS, CWE, proof of exploitation, or downstream package status is included. Avoid assuming impact beyond the documented mount-time heap out-of-bounds read.

Mitigation direction

  • Apply Linux kernel updates containing the referenced stable ntfs3 boundary-check commits.
  • Check distribution advisories for exact fixed kernel packages before production rollout.
  • Restrict or disable automatic mounting of untrusted NTFS media and disk images.
  • Use isolated systems for handling untrusted filesystem images until patched.
  • Review removable-media and VM image import workflows for unnecessary NTFS mounting.

Validation and detection

  • Inventory Linux systems that mount NTFS filesystems with the ntfs3 driver.
  • Map running kernel packages to vendor advisories or referenced stable commits.
  • Confirm patched source includes boundary checks before run_unpack_s64() calls in run_unpack().
  • Review desktop, forensic, backup, and virtualization workflows for untrusted NTFS image handling.
  • Verify automount policies do not mount untrusted NTFS media on sensitive systems.
Prepared
Confidence
medium
Sources
9

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2026-46072 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
0ADP providers
8Source links

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux82cae269cfa953032fbb8980a7d554d60fb00b17, 82cae269cfa953032fbb8980a7d554d60fb00b17, 82cae269cfa953032fbb8980a7d554d60fb00b17, 82cae269cfa953032fbb8980a7d554d60fb00b17, 82cae269cfa953032fbb8980a7d554d60fb00b17, 82cae269cfa953032fbb8980a7d554d60fb00b17, 82cae269cfa953032fbb8980a7d554d60fb00b17unaffected
LinuxLinux5.15, 0, 5.15.209, 6.1.175, 6.6.140, 6.12.86, 6.18.27, 7.0.4, 7.1affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.