Answer in brief
CVE-2025-38615 records a High severity (CVSS 7.8) vulnerability in fs/ntfs3: cancle set bad inode after removing name fails. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 7.8. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Product | Affected versions | Fixed versions |
|---|---|---|
| cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* | Not reported | Not reported |
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=78ab59fee07f22464f32eafebab2bd97ba94ff2d <b35a50d639ca5259466ef5fea85529bb4fb17d5b || >=78ab59fee07f22464f32eafebab2bd97ba94ff2d <3ed2cc6a6e93fbeb8c0cafce1e7fb1f64a331dcc || >=78ab59fee07f22464f32eafebab2bd97ba94ff2d <358d4f821c03add421a4c49290538a705852ccf1 || >=78ab59fee07f22464f32eafebab2bd97ba94ff2d <a285395020780adac1ffbc844069c3d700bf007a || >=78ab59fee07f22464f32eafebab2bd97ba94ff2d <d99208b91933fd2a58ed9ed321af07dacd06ddc3 | b35a50d639ca5259466ef5fea85529bb4fb17d5b, 3ed2cc6a6e93fbeb8c0cafce1e7fb1f64a331dcc, 358d4f821c03add421a4c49290538a705852ccf1, a285395020780adac1ffbc844069c3d700bf007a, d99208b91933fd2a58ed9ed321af07dacd06ddc3 |
| Linux/Linuxgeneric | 5.15 | Not reported |
| Linux/Linuxgeneric | >=78ab59fee07f22464f32eafebab2bd97ba94ff2d <47856e10f8d5e066aa26b1f9c02d933fe0620399 || >=78ab59fee07f22464f32eafebab2bd97ba94ff2d <b35a50d639ca5259466ef5fea85529bb4fb17d5b || >=78ab59fee07f22464f32eafebab2bd97ba94ff2d <3ed2cc6a6e93fbeb8c0cafce1e7fb1f64a331dcc || >=78ab59fee07f22464f32eafebab2bd97ba94ff2d <358d4f821c03add421a4c49290538a705852ccf1 || >=78ab59fee07f22464f32eafebab2bd97ba94ff2d <a285395020780adac1ffbc844069c3d700bf007a || >=78ab59fee07f22464f32eafebab2bd97ba94ff2d <d99208b91933fd2a58ed9ed321af07dacd06ddc3 | 47856e10f8d5e066aa26b1f9c02d933fe0620399, b35a50d639ca5259466ef5fea85529bb4fb17d5b, 3ed2cc6a6e93fbeb8c0cafce1e7fb1f64a331dcc, 358d4f821c03add421a4c49290538a705852ccf1, a285395020780adac1ffbc844069c3d700bf007a, d99208b91933fd2a58ed9ed321af07dacd06ddc3 |
Published upstream
Aug 19, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Oct 30, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
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".
Quoted source text, attributed separately from HOL analysis.