LiveActive security incident?Get immediate response
CVE Record

CVE-2025-38615: fs/ntfs3: cancle set bad inode after removing name fails

In the Linux kernel, the following vulnerability has been resolved: fs/ntfs3: cancle set bad inode after removing name fails The reproducer uses a file0 on a ntfs3 file system with a corrupted i_link. When renaming, the file0's inode is marked as a bad inode because the file name cannot be deleted. The underlying bug is that make_bad_inode() is called on a live inode. In some cases it's "icache lookup finds a normal inode, d_splice_alias() is called to attach it to dentry, while another thread decides to call make_bad_inode() on it - that would evict it from icache, but we'd already found it there earlier". In some it's outright "we have an inode attached to dentry - that's how we got it in the first place; let's call make_bad_inode() on it just for shits and giggles".

HighCVSS 7.8Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

A flaw in Linux's NTFS3 filesystem handling can corrupt kernel inode state during a rename involving already-corrupted NTFS metadata. A local, low-privileged user could potentially cause serious confidentiality, integrity, or availability impact. Exposure depends on NTFS3 being mounted and the triggering filesystem condition being reachable.

Executive priority

Prioritize exposed multi-user systems and endpoints handling untrusted NTFS media. Remediate through supported kernel updates during the next expedited maintenance window. Immediate emergency action is less justified without evidence of active exploitation, but the potential system-wide impact warrants prompt inventory and patch verification.

Technical view

During an NTFS3 rename, failure to remove a filename can call make_bad_inode() on a live inode. Concurrent inode-cache and dentry handling may then operate on an inode being evicted or invalidated. The supplied CVSS 3.1 score is 7.8, requiring local access and low privileges without user interaction.

Likely exposure

Most relevant to Linux systems mounting NTFS filesystems through ntfs3, particularly where local users or untrusted removable media can introduce or access corrupted metadata. Systems not using ntfs3 are unlikely to reach the described path. The supplied affected-version data is ambiguous and should be reconciled with distribution advisories.

Exploitation context

The source bundle provides a reproducer condition involving corrupted i_link metadata, but no exploit procedure. CISA KEV status is false, and the cited sources do not establish active exploitation. Practical reliability, impact mechanism, and whether ordinary users can create the prerequisite corruption remain unclear.

Researcher notes

The key prerequisite is a live inode reached through NTFS3 rename handling after filename removal fails on corrupted i_link metadata. Five stable-tree commits are cited, suggesting branch-specific backports. Exact introduced and fixed release boundaries are not reliably expressed in the supplied version data; validate commit ancestry or vendor package mappings.

Mitigation direction

  • Apply a vendor-supported kernel containing the appropriate cited stable fix.
  • Check distribution security guidance to map the fix to packaged kernel versions.
  • Restrict mounting or use of untrusted NTFS media until remediation.
  • Reduce unnecessary local account access on systems that must mount NTFS3 filesystems.

Validation and detection

  • Inventory systems currently mounting NTFS filesystems with the ntfs3 driver.
  • Record installed kernel and distribution package versions on exposed systems.
  • Confirm vendor advisories or package changelogs include the applicable stable fix.
  • Test rename and filesystem workflows safely after upgrading.
  • Monitor kernel and filesystem logs for NTFS3 errors or inode-related failures.
Prepared
Confidence
medium
Sources
7

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-2025-38615 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
7.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:L/AC:L/PR:L/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
6Source 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
7.8CVSS 3.1HighCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H1.85.9Linux

Vulnerability scoring details

Base CVSS 3.1 score

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

Vector: CVSS:3.1/AV:L/AC:L/PR:L/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.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux78ab59fee07f22464f32eafebab2bd97ba94ff2d, 78ab59fee07f22464f32eafebab2bd97ba94ff2d, 78ab59fee07f22464f32eafebab2bd97ba94ff2d, 78ab59fee07f22464f32eafebab2bd97ba94ff2d, 78ab59fee07f22464f32eafebab2bd97ba94ff2dunaffected
LinuxLinux5.15, 0, 6.6.102, 6.12.42, 6.15.10, 6.16.1, 6.17affected
Weakness

CWE details

No CWE listed

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