fs/ntfs3: call _ntfs_bad_inode() when failing to rename
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 6.18.57, 7.1.5
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
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.
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
From 519b078998ce6e729f98dccf35505b4756985d11 · fixed in 580896e33003845de66c75cd61544cf9d9bfbe15; From 519b078998ce6e729f98dccf35505b4756985d11 · fixed in ff825bf0521f6da2f30878cbad18ab7b341bc31b; From 519b078998ce6e729f98dccf35505b4756985d11 · fixed in e8ed78f40eecd0176fda71d673f6957c98e7ffbe
- Linux Linux
6.17
- KernelLinux
From 6.17.0 · fixed in 6.18.57; From 6.19.0 · fixed in 7.1.5