Skip to content
Noroxi
NVD / CVE Program· CNA Linux

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

MediumCVSS 5.5 · v3.1—No exploit Fix available

Noroxi assessment

Priority: Monitor (action score 22/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.19% (FIRST EPSS).
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: Linux Linux 358d4f821c03add421a4c49290538a705852ccf1, 3ed2cc6a6e93fbeb8c0cafce1e7fb1f64a331dcc, 47856e10f8d5e066aa26b1f9c02d933fe0620399.
  • Severity is disputed: the assigning authority (CNA) scores it 7.8, NVD 5.5.

Low priority for now. Upgrade to Linux Linux 358d4f821c03add421a4c49290538a705852ccf1, 3ed2cc6a6e93fbeb8c0cafce1e7fb1f64a331dcc, 47856e10f8d5e066aa26b1f9c02d933fe0620399 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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

Published
Aug 19, 2025
Updated
Oct 30, 2026
EPSS
0.1% · 9th percentile
CWE
—

Report tools

JSON

Action score

22

Monitor

Low priority for now.

CVSS
22 / 40 · 5.5 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.1%

CNA vs NVD score

NVD
5.5
CNA · Linux
7.8
2.3 point gap

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

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2025-38615

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits every 10 minutes on paid plans, on the hour on the free plan.

Your free account also gets you

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools, at most 30 a day (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records
Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
linuxlinux kernel

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • linux linux kernel5.15 and later · before 6.6.102
  • linux linux kernel6.7 and later · before 6.12.42
  • linux linux kernel6.13 and later · before 6.15.10
  • linux linux kernel6.16 and later · before 6.16.1

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 5.15affected
    • 78ab59fee07f22464f32eafebab2bd97ba94ff2d and later · before 47856e10f8d5e066aa26b1f9c02d933fe0620399affected · git
    • 78ab59fee07f22464f32eafebab2bd97ba94ff2d and later · before b35a50d639ca5259466ef5fea85529bb4fb17d5baffected · git
    • 78ab59fee07f22464f32eafebab2bd97ba94ff2d and later · before 3ed2cc6a6e93fbeb8c0cafce1e7fb1f64a331dccaffected · git
    • 78ab59fee07f22464f32eafebab2bd97ba94ff2d and later · before 358d4f821c03add421a4c49290538a705852ccf1affected · git
    • 78ab59fee07f22464f32eafebab2bd97ba94ff2d and later · before a285395020780adac1ffbc844069c3d700bf007aaffected · git
    • 78ab59fee07f22464f32eafebab2bd97ba94ff2d and later · before d99208b91933fd2a58ed9ed321af07dacd06ddc3affected · git
    • before 5.15not affected · semver
    • 6.1.191 and later · up to and including 6.1.*not affected · semver
    • 6.6.102 and later · up to and including 6.6.*not affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12linuxfrom 0—
Debian:13linuxbefore 6.12.43-16.12.43-1
Debian:14linuxbefore 6.16.3-16.16.3-1

Same product

linux: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
    90Now
  • CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe…KEV
    89Now
  • CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
    85Now

Published before and after this one in the same product

  • ← EarlierCVE-2025-38609Aug 19, 2025 · PM / devfreq: Check governor before using governor->name
    22Monitor
  • ← EarlierCVE-2025-38614Aug 19, 2025 · eventpoll: Fix semi-unbounded recursion
    22Monitor
  • Later →CVE-2025-38616Aug 22, 2025 · tls: handle data disappearing from under the TLS ULP
    28Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux358d4f821c03add421a4c49290538a705852ccf1Vendor (CNA)
Linux Linux3ed2cc6a6e93fbeb8c0cafce1e7fb1f64a331dccVendor (CNA)
Linux Linux47856e10f8d5e066aa26b1f9c02d933fe0620399Vendor (CNA)
Linux Linuxa285395020780adac1ffbc844069c3d700bf007aVendor (CNA)
Linux Linuxb35a50d639ca5259466ef5fea85529bb4fb17d5bVendor (CNA)
Linux Linuxd99208b91933fd2a58ed9ed321af07dacd06ddc3Vendor (CNA)
debian:linux6.12.43-1 · Debian:13Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
none
Integrity
none
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
None
Integrity impact
None
Availability impact
High

Weakness class (CWE)

—

CVSS vector

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

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (5 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records