Description (CNA)
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".
Affected (CNA)
| Vendor / product | Versions |
|---|---|
| Linux / Linux | affected 78ab59fee07f22464f32eafebab2bd97ba94ff2d before b35a50d639ca5259466ef5fea85529bb4fb17d5b; affected 78ab59fee07f22464f32eafebab2bd97ba94ff2d before 3ed2cc6a6e93fbeb8c0cafce1e7fb1f64a331dcc; affected 78ab59fee07f22464f32eafebab2bd97ba94ff2d before 358d4f821c03add421a4c49290538a705852ccf1; affected 78ab59fee07f22464f32eafebab2bd97ba94ff2d before a285395020780adac1ffbc844069c3d700bf007a; affected 78ab59fee07f22464f32eafebab2bd97ba94ff2d before d99208b91933fd2a58ed9ed321af07dacd06ddc3 |
| Linux / Linux | affected 5.15; unaffected 0 before 5.15; unaffected 6.6.102 through 6.6.*; unaffected 6.12.42 through 6.12.*; unaffected 6.15.10 through 6.15.*; unaffected 6.16.1 through 6.16.*; unaffected 6.17 through * |
CWE
No CWE identifiers supplied.
References
- https://git.kernel.org/stable/c/b35a50d639ca5259466ef5fea85529bb4fb17d5b
- https://git.kernel.org/stable/c/3ed2cc6a6e93fbeb8c0cafce1e7fb1f64a331dcc
- https://git.kernel.org/stable/c/358d4f821c03add421a4c49290538a705852ccf1
- https://git.kernel.org/stable/c/a285395020780adac1ffbc844069c3d700bf007a
- https://git.kernel.org/stable/c/d99208b91933fd2a58ed9ed321af07dacd06ddc3