LiveActive security incident?Get immediate response
CVE Record

CVE-2025-40068: fs: ntfs3: Fix integer overflow in run_unpack()

In the Linux kernel, the following vulnerability has been resolved: fs: ntfs3: Fix integer overflow in run_unpack() The MFT record relative to the file being opened contains its runlist, an array containing information about the file's location on the physical disk. Analysis of all Call Stack paths showed that the values of the runlist array, from which LCNs are calculated, are not validated before run_unpack function. The run_unpack function decodes the compressed runlist data format from MFT attributes (for example, $DATA), converting them into a runs_tree structure, which describes the mapping of virtual clusters (VCN) to logical clusters (LCN). The NTFS3 subsystem also has a shortcut for deleting files from MFT records - in this case, the RUN_DEALLOCATE command is sent to the run_unpack input, and the function logic provides that all data transferred to the runlist about file or directory is deleted without creating a runs_tree structure. Substituting the runlist in the $DATA attribute of the MFT record for an arbitrary file can lead either to access to arbitrary data on the disk bypassing access checks to them (since the inode access check occurs above) or to destruction of arbitrary data on the disk. Add overflow check for addition operation. Found by Linux Verification Center (linuxtesting.org) with SVACE.

HighCVSS 8.4Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

A flaw in Linux’s NTFS3 filesystem driver can mishandle malicious NTFS file-location metadata. If triggered, it may let an attacker read protected disk data or corrupt arbitrary disk data, potentially causing serious confidentiality, integrity, and availability impact.

Executive priority

Prioritize prompt remediation on systems that routinely process externally supplied or otherwise untrusted NTFS volumes, especially where sensitive or critical disk data is present. For systems without NTFS3 use, confirm non-exposure before lowering priority. Current evidence supports serious local risk, not an Internet-wide exploitation emergency.

Technical view

An integer overflow in run_unpack() occurs while decoding insufficiently validated NTFS MFT runlist data into VCN-to-LCN mappings. Crafted $DATA runlist values may produce invalid logical-cluster calculations, bypassing higher-level inode access checks or targeting unintended disk locations. The referenced Linux stable changes add an overflow check to the addition operation.

Likely exposure

Exposure is most likely on affected Linux kernels using NTFS3 to process untrusted or tampered NTFS metadata. Running Linux alone does not establish exposure. The supplied version data is not a complete distribution-package mapping, so kernel configuration, actual NTFS3 use, and inclusion of the referenced fixes require validation.

Exploitation context

The supplied CVSS 3.1 score is 8.4, with local access, low complexity, no privileges, and no user interaction. Triggering requires maliciously altered NTFS runlist metadata to reach NTFS3. The CVE is not listed as KEV, and the bundle provides no evidence of exploitation in the wild.

Researcher notes

The security consequence comes from unchecked arithmetic during runlist decoding, potentially misdirecting logical-cluster access. The references appear to be stable-branch fixes for the same condition. The bundle provides no CWE assignment, proof of concept, distribution package mapping, detailed delivery scenario, or evidence of observed exploitation.

Mitigation direction

  • Apply a Linux kernel update containing the applicable referenced stable fix.
  • Until updated, prevent affected systems from processing untrusted NTFS volumes where operationally feasible.
  • Consult Linux distributor guidance for package-specific fixed builds; the bundle does not name distribution package versions.

Validation and detection

  • Inventory running kernel builds and compare them with the affected-version data and applicable stable fix commits.
  • Confirm whether NTFS3 is built, loadable, or currently used on each candidate system.
  • Identify workflows that allow untrusted or tampered NTFS media or images to reach affected systems.
  • After updating, verify the running kernel includes the relevant stable fix and retest required NTFS operations.
Prepared
Confidence
medium
Sources
8

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.

description · low confidence lookup

File access behavior lookup

The CVE wording references file access or upload behavior, so file telemetry and web shell review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2025-40068 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
High
CVSS
8.4 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

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.

1CVSS vectors
3Timeline events
0ADP providers
7Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
8.4CVSS 3.1HighCVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H2.55.9Linux

Vulnerability scoring details

Base CVSS 3.1 score

8.4High
CVSS 3.1 vector shape for CVE-2025-40068Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

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.

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux4342306f0f0d5ff4315a204d315c1b51b914fca5, 4342306f0f0d5ff4315a204d315c1b51b914fca5, 4342306f0f0d5ff4315a204d315c1b51b914fca5, 4342306f0f0d5ff4315a204d315c1b51b914fca5, 4342306f0f0d5ff4315a204d315c1b51b914fca5, 4342306f0f0d5ff4315a204d315c1b51b914fca5unaffected
LinuxLinux5.15, 0, 5.15.195, 6.1.156, 6.6.112, 6.12.53, 6.17.3, 6.18affected
Weakness

CWE details

No CWE listed

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