Answer in brief
CVE-2026-72477 records a Unknown severity vulnerability in fs/ntfs3: call _ntfs_bad_inode() when failing to rename. The current sources do not mark it as known exploited. The current feed maps 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.
A CVSS score is not reported in the current record. 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). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=519b078998ce6e729f98dccf35505b4756985d11 <ff825bf0521f6da2f30878cbad18ab7b341bc31b || >=519b078998ce6e729f98dccf35505b4756985d11 <e8ed78f40eecd0176fda71d673f6957c98e7ffbe | ff825bf0521f6da2f30878cbad18ab7b341bc31b, e8ed78f40eecd0176fda71d673f6957c98e7ffbe |
| Linux/Linuxgeneric | 6.17 | Not reported |
Published upstream
Aug 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 15, 2026
In the Linux kernel, the following vulnerability has been resolved: fs/ntfs3: call _ntfs_bad_inode() when failing to rename It is safe to call _ntfs_bad_inode on live inodes since: commit 519b078998ce ("fs/ntfs3: Exclude call make_bad_inode for live nodes.") The WARN_ON was added when it wasn't safe by: commit d99208b91933 ("fs/ntfs3: cancle set bad inode after removing name fails") Replace the WARN_ON with a call to _ntfs_bad_inode() to prevent further operations on the inconsistent inode.
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2026-72477 records a Unknown severity vulnerability in fs/ntfs3: call _ntfs_bad_inode() when failing to rename. The current sources do not mark it as known exploited. The current feed maps 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.
A CVSS score is not reported in the current record. 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). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=519b078998ce6e729f98dccf35505b4756985d11 <ff825bf0521f6da2f30878cbad18ab7b341bc31b || >=519b078998ce6e729f98dccf35505b4756985d11 <e8ed78f40eecd0176fda71d673f6957c98e7ffbe | ff825bf0521f6da2f30878cbad18ab7b341bc31b, e8ed78f40eecd0176fda71d673f6957c98e7ffbe |
| Linux/Linuxgeneric | 6.17 | Not reported |
Published upstream
Aug 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 15, 2026
In the Linux kernel, the following vulnerability has been resolved: fs/ntfs3: call _ntfs_bad_inode() when failing to rename It is safe to call _ntfs_bad_inode on live inodes since: commit 519b078998ce ("fs/ntfs3: Exclude call make_bad_inode for live nodes.") The WARN_ON was added when it wasn't safe by: commit d99208b91933 ("fs/ntfs3: cancle set bad inode after removing name fails") Replace the WARN_ON with a call to _ntfs_bad_inode() to prevent further operations on the inconsistent inode.
Quoted source text, attributed separately from HOL analysis.