---
id: CVE-2025-38615
title: 'fs/ntfs3: cancle set bad inode after removing name fails'
summary: |-
  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 i…
severity: high
cvss: 7.8
cvssVector: 'CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H'
cvssSource: cna
vendor: Linux
product: Linux
affected:
  - >-
    Linux >= 78ab59fee07f22464f32eafebab2bd97ba94ff2d <
    47856e10f8d5e066aa26b1f9c02d933fe0620399
  - >-
    Linux >= 78ab59fee07f22464f32eafebab2bd97ba94ff2d <
    b35a50d639ca5259466ef5fea85529bb4fb17d5b
  - >-
    Linux >= 78ab59fee07f22464f32eafebab2bd97ba94ff2d <
    3ed2cc6a6e93fbeb8c0cafce1e7fb1f64a331dcc
  - >-
    Linux >= 78ab59fee07f22464f32eafebab2bd97ba94ff2d <
    358d4f821c03add421a4c49290538a705852ccf1
  - >-
    Linux >= 78ab59fee07f22464f32eafebab2bd97ba94ff2d <
    a285395020780adac1ffbc844069c3d700bf007a
  - >-
    Linux >= 78ab59fee07f22464f32eafebab2bd97ba94ff2d <
    d99208b91933fd2a58ed9ed321af07dacd06ddc3
  - Linux 5.15
published: '2025-08-19'
updated: '2026-10-30'
sourceUpdated: '2026-10-30T12:22:08.400Z'
source: CVEORG
sourceUrl: 'https://www.cve.org/CVERecord?id=CVE-2025-38615'
references:
  - url: 'https://git.kernel.org/stable/c/47856e10f8d5e066aa26b1f9c02d933fe0620399'
  - url: 'https://git.kernel.org/stable/c/b35a50d639ca5259466ef5fea85529bb4fb17d5b'
  - url: 'https://git.kernel.org/stable/c/3ed2cc6a6e93fbeb8c0cafce1e7fb1f64a331dcc'
  - url: 'https://git.kernel.org/stable/c/358d4f821c03add421a4c49290538a705852ccf1'
  - url: 'https://git.kernel.org/stable/c/a285395020780adac1ffbc844069c3d700bf007a'
  - url: 'https://git.kernel.org/stable/c/d99208b91933fd2a58ed9ed321af07dacd06ddc3'
tags:
  - cve.org
epss: 0.00183
epssPercentile: 0.07956
ingestedAt: '2026-11-03T19:53:18.506Z'
---

## Overview

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".

## Affected

- `Linux >= 78ab59fee07f22464f32eafebab2bd97ba94ff2d < 47856e10f8d5e066aa26b1f9c02d933fe0620399`
- `Linux >= 78ab59fee07f22464f32eafebab2bd97ba94ff2d < b35a50d639ca5259466ef5fea85529bb4fb17d5b`
- `Linux >= 78ab59fee07f22464f32eafebab2bd97ba94ff2d < 3ed2cc6a6e93fbeb8c0cafce1e7fb1f64a331dcc`
- `Linux >= 78ab59fee07f22464f32eafebab2bd97ba94ff2d < 358d4f821c03add421a4c49290538a705852ccf1`
- `Linux >= 78ab59fee07f22464f32eafebab2bd97ba94ff2d < a285395020780adac1ffbc844069c3d700bf007a`
- `Linux >= 78ab59fee07f22464f32eafebab2bd97ba94ff2d < d99208b91933fd2a58ed9ed321af07dacd06ddc3`
- `Linux 5.15`

## Remediation

Refer to the linked advisories for vendor-supplied fixes and affected version ranges.