f2fs: fix to avoid f2fs_bug_on() in dec_valid_node_count()
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 39a53e0ce0df01b3cf4bb898c7ae2fd2189647d5 · < 4d17e6fe9293d57081ffdc11e1cf313e25e8fd9e| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
f2fs: fix to avoid f2fs_bug_on() in dec_valid_node_count()
As Yanming reported in bugzilla:
https://bugzilla.kernel.org/show_bug.cgi?id=215897
I have encountered a bug in F2FS file system in kernel v5.17.
The kernel should enable CONFIG_KASAN=y and CONFIG_KASAN_INLINE=y. You can reproduce the bug by running the following commands:
The kernel message is shown below:
kernel BUG at fs/f2fs/f2fs.h:2511! Call Trace: f2fs_remove_inode_page+0x2a2/0x830 f2fs_evict_inode+0x9b7/0x1510 evict+0x282/0x4e0 do_unlinkat+0x33a/0x540 __x64_sys_unlinkat+0x8e/0xd0 do_syscall_64+0x3b/0x90 entry_SYSCALL_64_after_hwframe+0x44/0xae
From the CVE record · Linux
The F2FS filesystem can hit a kernel BUG when its valid block or node count has been fuzzed to zero and a node is removed. A local filesystem operation such as unlink can then trigger a kernel panic; the report observed this in kernel v5.17.
Engineers running Linux kernels with F2FS, particularly v5.17, should check their systems.