Linux Kernel up to 6.6.101/6.12.41/6.15.9/6.16.0 ntfs3 make_bad_inode denial of service

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
4.4$0-$5k0.00

Summaryinfo

A vulnerability identified as problematic has been detected in Linux Kernel up to 6.6.101/6.12.41/6.15.9/6.16.0. This impacts the function make_bad_inode of the component ntfs3. Performing a manipulation results in denial of service. This vulnerability is reported as CVE-2025-38615. No exploit exists. You should upgrade the affected component.

Detailsinfo

A vulnerability, which was classified as problematic, was found in Linux Kernel up to 6.6.101/6.12.41/6.15.9/6.16.0. This affects the function make_bad_inode of the component ntfs3. The manipulation with an unknown input leads to a denial of service vulnerability. CWE is classifying the issue as CWE-404. The product does not release or incorrectly releases a resource before it is made available for re-use. This is going to have an impact on availability. The summary by CVE is:

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

The advisory is shared at git.kernel.org. This vulnerability is uniquely identified as CVE-2025-38615 since 04/16/2025. Technical details are known, but no exploit is available.

The vulnerability scanner Nessus provides a plugin with the ID 260128 (Linux Distros Unpatched Vulnerability : CVE-2025-38615), which helps to determine the existence of the flaw in a target environment.

Upgrading to version 6.6.102, 6.12.42, 6.15.10, 6.16.1 or 6.17-rc1 eliminates this vulnerability. Applying the patch b35a50d639ca5259466ef5fea85529bb4fb17d5b/3ed2cc6a6e93fbeb8c0cafce1e7fb1f64a331dcc/358d4f821c03add421a4c49290538a705852ccf1/a285395020780adac1ffbc844069c3d700bf007a/d99208b91933fd2a58ed9ed321af07dacd06ddc3 is able to eliminate this problem. The bugfix is ready for download at git.kernel.org. The best possible mitigation is suggested to be upgrading to the latest version.

The vulnerability is also documented in the databases at Tenable (260128) and CERT Bund (WID-SEC-2025-1869). If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Affected

  • Debian Linux
  • Amazon Linux 2
  • Red Hat Enterprise Linux
  • Ubuntu Linux
  • SUSE Linux
  • Oracle Linux
  • SUSE openSUSE
  • RESF Rocky Linux
  • Dell Avamar
  • Open Source Linux Kernel
  • Dell NetWorker
  • Dell Secure Connect Gateway
  • IBM QRadar SIEM

Productinfo

Type

Vendor

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 4.5
VulDB Meta Temp Score: 4.4

VulDB Base Score: 3.5
VulDB Temp Score: 3.4
VulDB Vector: 🔒
VulDB Reliability: 🔍

NVD Base Score: 5.5
NVD Vector: 🔒

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍

Exploitinginfo

Class: Denial of service
CWE: CWE-404
CAPEC: 🔒
ATT&CK: 🔒

Physical: Partially
Local: Yes
Remote: Partially

Availability: 🔒
Status: Not defined

EPSS Score: 🔒
EPSS Percentile: 🔒

Price Prediction: 🔍
Current Price Estimation: 🔒

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Nessus ID: 260128
Nessus Name: Linux Distros Unpatched Vulnerability : CVE-2025-38615

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔒

Upgrade: Kernel 6.6.102/6.12.42/6.15.10/6.16.1/6.17-rc1
Patch: b35a50d639ca5259466ef5fea85529bb4fb17d5b/3ed2cc6a6e93fbeb8c0cafce1e7fb1f64a331dcc/358d4f821c03add421a4c49290538a705852ccf1/a285395020780adac1ffbc844069c3d700bf007a/d99208b91933fd2a58ed9ed321af07dacd06ddc3

Timelineinfo

04/16/2025 CVE reserved
08/19/2025 +125 days Advisory disclosed
08/19/2025 +0 days VulDB entry created
01/21/2026 +155 days VulDB entry last update

Sourcesinfo

Vendor: kernel.org

Advisory: git.kernel.org
Status: Confirmed

CVE: CVE-2025-38615 (🔒)
GCVE (CVE): GCVE-0-2025-38615
GCVE (VulDB): GCVE-100-320637
CERT Bund: WID-SEC-2025-1869 - Linux Kernel: Mehrere Schwachstellen

Entryinfo

Created: 08/19/2025 19:34
Updated: 01/21/2026 09:46
Changes: 08/19/2025 19:34 (59), 09/01/2025 16:25 (2), 10/18/2025 07:35 (7), 10/27/2025 03:08 (1), 11/01/2025 15:26 (1), 11/26/2025 20:19 (12), 01/21/2026 09:46 (1)
Complete: 🔍
Cache ID: 216::103

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Do you want to use VulDB in your project?

Use the official API to access entries easily!