fs/ntfs3: cancle set bad inode after removing name fails
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 78ab59fee07f22464f32eafebab2bd97ba94ff2d · < d99208b91933fd2a58ed9ed321af07dacd06ddc3| No fix yet |
| Linux Linux |
|
|
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".
From the CVE record · Linux
The Linux kernel's ntfs3 driver can mark a live inode as bad when renaming a file on an NTFS filesystem with a corrupted i_link fails to remove the file name. A user able to trigger that rename can cause inconsistent inode-cache and dentry state; the input does not establish a remote attack path or specify authentication requirements.
Engineers running Linux kernels with the ntfs3 driver should check their kernel versions; affected versions are not specified.