CVE-2024-42297

f2fs: fix to don't dirty inode for readonly filesystem

Description

In the Linux kernel, the following vulnerability has been resolved: f2fs: fix to don't dirty inode for readonly filesystem syzbot reports f2fs bug as below: kernel BUG at fs/f2fs/inode.c:933! RIP: 0010:f2fs_evict_inode+0x1576/0x1590 fs/f2fs/inode.c:933 Call Trace: evict+0x2a4/0x620 fs/inode.c:664 dispose_list fs/inode.c:697 [inline] evict_inodes+0x5f8/0x690 fs/inode.c:747 generic_shutdown_super+0x9d/0x2c0 fs/super.c:675 kill_block_super+0x44/0x90 fs/super.c:1667 kill_f2fs_super+0x303/0x3b0 fs/f2fs/super.c:4894 deactivate_locked_super+0xc1/0x130 fs/super.c:484 cleanup_mnt+0x426/0x4c0 fs/namespace.c:1256 task_work_run+0x24a/0x300 kernel/task_work.c:180 ptrace_notify+0x2cd/0x380 kernel/signal.c:2399 ptrace_report_syscall include/linux/ptrace.h:411 [inline] ptrace_report_syscall_exit include/linux/ptrace.h:473 [inline] syscall_exit_work kernel/entry/common.c:251 [inline] syscall_exit_to_user_mode_prepare kernel/entry/common.c:278 [inline] __syscall_exit_to_user_mode_work kernel/entry/common.c:283 [inline] syscall_exit_to_user_mode+0x15c/0x280 kernel/entry/common.c:296 do_syscall_64+0x50/0x110 arch/x86/entry/common.c:88 entry_SYSCALL_64_after_hwframe+0x63/0x6b The root cause is: - do_sys_open - f2fs_lookup - __f2fs_find_entry - f2fs_i_depth_write - f2fs_mark_inode_dirty_sync - f2fs_dirty_inode - set_inode_flag(inode, FI_DIRTY_INODE) - umount - kill_f2fs_super - kill_block_super - generic_shutdown_super - sync_filesystem : sb is readonly, skip sync_filesystem() - evict_inodes - iput - f2fs_evict_inode - f2fs_bug_on(sbi, is_inode_flag_set(inode, FI_DIRTY_INODE)) : trigger kernel panic When we try to repair i_current_depth in readonly filesystem, let's skip dirty inode to avoid panic in later f2fs_evict_inode().

5.5

CVSS

Severity: Medium

CVSS 3.1 •

EPSS 0.05%

Affected: Linux Linux

References

Link	Tags
https://git.kernel.org/stable/c/2d2916516577f2239b3377d9e8d12da5e6ccdfcf	patch
https://git.kernel.org/stable/c/54162974aea37a8cae00742470a78c7f6bd6f915	patch
https://git.kernel.org/stable/c/54bc4e88447e385c4d4ffa85d93e0dce628fcfa6	patch
https://git.kernel.org/stable/c/ec56571b4b146a1cfbedab49d5fcaf19fe8bf4f1	patch
https://git.kernel.org/stable/c/9ce8135accf103f7333af472709125878704fdd4	patch
https://git.kernel.org/stable/c/e62ff092a42f4a1bae3b310cf46673b4f3aac3b5	patch
https://git.kernel.org/stable/c/2434344559f6743efb3ac15d11af9a0db9543bd3	patch
https://git.kernel.org/stable/c/192b8fb8d1c8ca3c87366ebbef599fa80bb626b8	patch

Frequently Asked Questions

What is the severity of CVE-2024-42297?: CVE-2024-42297 has been scored as a medium severity vulnerability.
How to fix CVE-2024-42297?: To fix CVE-2024-42297, make sure you are using an up-to-date version of the affected component(s) by checking the vendor release notes. As for now, there are no other specific guidelines available.
Is CVE-2024-42297 being actively exploited in the wild?: As for now, there are no information to confirm that CVE-2024-42297 is being actively exploited. According to its EPSS score, there is a ~0% probability that this vulnerability will be exploited by malicious actors in the next 30 days.
What software or system is affected by CVE-2024-42297?: CVE-2024-42297 affects Linux Linux, Linux Linux.