fs/ntfs3: call _ntfs_bad_inode() when failing to rename
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
6.18.577.1.57.2In 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.
From the CVE record · Linux
A failed rename in the Linux kernel's ntfs3 filesystem can leave an inode inconsistent. The fix marks that inode bad to prevent further operations; the input does not specify an attack path, authentication requirements, or user interaction.
Engineers running Linux kernels with the ntfs3 filesystem should check their kernel versions; affected versions are not specified.