Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

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

Description

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

Timeline

  1. ID reserved

    By Linux

  2. · 4 months later

    Published

  3. · 15 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2025-38615, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
NVDNVD · Modified3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.19% · top 91% of all CVEs (17 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.8.

Affected products

  • Linux · Linux

    • affected 78ab59fee07f22464f32eafebab2bd97ba94ff2d – < 47856e10f8d5e066aa26b1f9c02d933fe0620399
    • affected 78ab59fee07f22464f32eafebab2bd97ba94ff2d – < b35a50d639ca5259466ef5fea85529bb4fb17d5b
    • affected 78ab59fee07f22464f32eafebab2bd97ba94ff2d – < 3ed2cc6a6e93fbeb8c0cafce1e7fb1f64a331dcc
    • affected 78ab59fee07f22464f32eafebab2bd97ba94ff2d – < 358d4f821c03add421a4c49290538a705852ccf1
    • affected 78ab59fee07f22464f32eafebab2bd97ba94ff2d – < a285395020780adac1ffbc844069c3d700bf007a
    • affected 78ab59fee07f22464f32eafebab2bd97ba94ff2d – < d99208b91933fd2a58ed9ed321af07dacd06ddc3
  • Linux · Linux

    • affected 5.15
    • unaffected < 5.15
    • unaffected 6.1.191 – ≤ 6.1.*
    • unaffected 6.6.102 – ≤ 6.6.*
    • unaffected 6.12.42 – ≤ 6.12.*
    • unaffected 6.15.10 – ≤ 6.15.*
    • unaffected 6.16.1 – ≤ 6.16.*
    • unaffected 6.17 – ≤ *

References

References6

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2025-38615 badge
[![CVE-2025-38615](https://cveledger.app/badge/CVE-2025-38615.svg)](https://cveledger.app/cve/CVE-2025-38615)

Record last updated .