CVE-2024-53218— f2fs: fix race in concurrent f2fs_stop_gc_thread
Get alerts for future matching vulnerabilitiesLog in to subscribe
I. Basic Information for CVE-2024-53218
Vulnerability Information
Have questions about the vulnerability? See if Shenlong's analysis helps!
View Shenlong Deep Dive ↗ Although we use advanced large model technology, its output may still contain inaccurate or outdated information.Shenlong tries to ensure data accuracy, but please verify and judge based on the actual situation.
Vulnerability Title
f2fs: fix race in concurrent f2fs_stop_gc_thread
Source: NVD (National Vulnerability Database)
Vulnerability Description
In the Linux kernel, the following vulnerability has been resolved: f2fs: fix race in concurrent f2fs_stop_gc_thread In my test case, concurrent calls to f2fs shutdown report the following stack trace: Oops: general protection fault, probably for non-canonical address 0xc6cfff63bb5513fc: 0000 [#1] PREEMPT SMP PTI CPU: 0 UID: 0 PID: 678 Comm: f2fs_rep_shutdo Not tainted 6.12.0-rc5-next-20241029-g6fb2fa9805c5-dirty #85 Call Trace: <TASK> ? show_regs+0x8b/0xa0 ? __die_body+0x26/0xa0 ? die_addr+0x54/0x90 ? exc_general_protection+0x24b/0x5c0 ? asm_exc_general_protection+0x26/0x30 ? kthread_stop+0x46/0x390 f2fs_stop_gc_thread+0x6c/0x110 f2fs_do_shutdown+0x309/0x3a0 f2fs_ioc_shutdown+0x150/0x1c0 __f2fs_ioctl+0xffd/0x2ac0 f2fs_ioctl+0x76/0xe0 vfs_ioctl+0x23/0x60 __x64_sys_ioctl+0xce/0xf0 x64_sys_call+0x2b1b/0x4540 do_syscall_64+0xa7/0x240 entry_SYSCALL_64_after_hwframe+0x76/0x7e The root cause is a race condition in f2fs_stop_gc_thread() called from different f2fs shutdown paths: [CPU0] [CPU1] ---------------------- ----------------------- f2fs_stop_gc_thread f2fs_stop_gc_thread gc_th = sbi->gc_thread gc_th = sbi->gc_thread kfree(gc_th) sbi->gc_thread = NULL < gc_th != NULL > kthread_stop(gc_th->f2fs_gc_task) //UAF The commit c7f114d864ac ("f2fs: fix to avoid use-after-free in f2fs_stop_gc_thread()") attempted to fix this issue by using a read semaphore to prevent races between shutdown and remount threads, but it fails to prevent all race conditions. Fix it by converting to write lock of s_umount in f2fs_do_shutdown().
Source: NVD (National Vulnerability Database)
CVSS Information
N/A
Source: NVD (National Vulnerability Database)
Vulnerability Type
N/A
Source: NVD (National Vulnerability Database)
Vulnerability Title
Linux kernel 安全漏洞
Source: CNNVD (China National Vulnerability Database)
Vulnerability Description
Linux kernel是美国Linux基金会的开源操作系统Linux所使用的内核。 Linux kernel存在安全漏洞，该漏洞源于f2fs文件系统中并发停止垃圾回收时的竞争条件问题。
Source: CNNVD (China National Vulnerability Database)
CVSS Information
N/A
Source: CNNVD (China National Vulnerability Database)
Vulnerability Type
N/A
Source: CNNVD (China National Vulnerability Database)
Affected Products
II. Public POCs for CVE-2024-53218
| # | POC Description | Source Link | Shenlong Link |
|---|
AI-Generated POCPremium
No public POC found.
Login to generate AI POCIII. Intelligence Information for CVE-2024-53218
请登录查看更多情报信息。
Same Patch Batch · Linux · 2024-12-27 · 221 CVEs total
| CVE-2024-56607 | wifi: ath12k: fix atomic calls in ath12k_mac_op_set_bitrate_mask() | |
| CVE-2024-56594 | drm/amdgpu: set the right AMDGPU sg segment limitation | |
| CVE-2024-56595 | jfs: add a check to prevent array-index-out-of-bounds in dbAdjTree | |
| CVE-2024-56596 | jfs: fix array-index-out-of-bounds in jfs_readdir | |
| CVE-2024-56597 | jfs: fix shift-out-of-bounds in dbSplit | |
| CVE-2024-56598 | jfs: array-index-out-of-bounds fix in dtReadFirst | |
| CVE-2024-56599 | wifi: ath10k: avoid NULL pointer error during sdio remove | |
| CVE-2024-56601 | net: inet: do not leave a dangling sk pointer in inet_create() | |
| CVE-2024-56600 | net: inet6: do not leave a dangling sk pointer in inet6_create() | |
| CVE-2024-56602 | net: ieee802154: do not leave a dangling sk pointer in ieee802154_create() | |
| CVE-2024-56603 | net: af_can: do not leave a dangling sk pointer in can_create() | |
| CVE-2024-56604 | Bluetooth: RFCOMM: avoid leaving dangling sk pointer in rfcomm_sock_alloc() | |
| CVE-2024-56605 | Bluetooth: L2CAP: do not leave dangling sk pointer on error in l2cap_sock_create() | |
| CVE-2024-56606 | af_packet: avoid erroring out after sock_init_data() in packet_create() | |
| CVE-2024-56618 | pmdomain: imx: gpcv2: Adjust delay after power up handshake | |
| CVE-2024-56615 | bpf: fix OOB devmap writes when deleting elements | |
| CVE-2024-56616 | drm/dp_mst: Fix MST sideband message body length check | |
| CVE-2024-56617 | cacheinfo: Allocate memory during CPU hotplug if not done from the primary CPU | |
| CVE-2024-56614 | xsk: fix OOB map writes when deleting elements | |
| CVE-2024-56619 | nilfs2: fix potential out-of-bounds memory access in nilfs_find_entry() |
Showing top 20 of 221 CVEs. View all on vendor page → →
IV. Related Vulnerabilities
Same product: Linux
- CVE-2026-43500
rxrpc: Also unshare DATA/RESPONSE packets when paged frags a - CVE-2026-43475
scsi: storvsc: Fix scheduling while atomic on PREEMPT_RT - CVE-2026-43474
fs: init flags_valid before calling vfs_fileattr_get - CVE-2026-43473
scsi: mpi3mr: Add NULL checks when resetting request and rep - CVE-2026-43472
unshare: fix unshare_fs() handling
Same vendor: Linux
- CVE-2026-43500
rxrpc: Also unshare DATA/RESPONSE packets when paged frags a - CVE-2026-43475
scsi: storvsc: Fix scheduling while atomic on PREEMPT_RT - CVE-2026-43474
fs: init flags_valid before calling vfs_fileattr_get - CVE-2026-43473
scsi: mpi3mr: Add NULL checks when resetting request and rep - CVE-2026-43472
unshare: fix unshare_fs() handling
V. Comments for CVE-2024-53218
No comments yet