Goal Reached Thanks to every supporter — we hit 100%!

Goal: 1000 CNY · Raised: 1359 CNY

100%

CVE-2023-53447— f2fs: don't reset unchangable mount option in f2fs_remount()

Quick assessment

Affected
Linux Linux
Exploitation
No confirmed in-the-wild exploitation; assess based on exposure
Recommended action
Check the vendor advisory and references for a fixed version. If immediate upgrade is impossible, restrict exposure and increase monitoring.

Linux kernel是美国Linux基金会的开源操作系统Linux所使用的内核。 Linux kernel存在安全漏洞,该漏洞源于f2fs_remount函数中重置不可更改的挂载选项,可能导致一般保护错误。

AI Predicted 6.5 Difficulty: Hard EPSS 0.10% · P1

Possible ATT&CK Techniques 1 AI

T1203 · Exploitation for Client Execution

Affected Version Matrix 6

VendorProduct Version RangeStatus
Linux Linux 98e4da8ca301e062d79ae168c67e56f3c3de3ce4< 115557cc226a927924f2d7d1980ccbf6e3b3bb36 affected
98e4da8ca301e062d79ae168c67e56f3c3de3ce4< 458c15dfbce62c35fefd9ca637b20a051309c9f1 affected
3.8 affected
< 3.8 unaffected
6.4.5≤ 6.4.* unaffected
6.5≤ * unaffected
Get alerts for future matching vulnerabilities Log in to subscribe

I. Basic Information for CVE-2023-53447

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: don't reset unchangable mount option in f2fs_remount()
Source: CVE Program / CVE List V5
Vulnerability Description
In the Linux kernel, the following vulnerability has been resolved: f2fs: don't reset unchangable mount option in f2fs_remount() syzbot reports a bug as below: general protection fault, probably for non-canonical address 0xdffffc0000000009: 0000 [#1] PREEMPT SMP KASAN RIP: 0010:__lock_acquire+0x69/0x2000 kernel/locking/lockdep.c:4942 Call Trace: lock_acquire+0x1e3/0x520 kernel/locking/lockdep.c:5691 __raw_write_lock include/linux/rwlock_api_smp.h:209 [inline] _raw_write_lock+0x2e/0x40 kernel/locking/spinlock.c:300 __drop_extent_tree+0x3ac/0x660 fs/f2fs/extent_cache.c:1100 f2fs_drop_extent_tree+0x17/0x30 fs/f2fs/extent_cache.c:1116 f2fs_insert_range+0x2d5/0x3c0 fs/f2fs/file.c:1664 f2fs_fallocate+0x4e4/0x6d0 fs/f2fs/file.c:1838 vfs_fallocate+0x54b/0x6b0 fs/open.c:324 ksys_fallocate fs/open.c:347 [inline] __do_sys_fallocate fs/open.c:355 [inline] __se_sys_fallocate fs/open.c:353 [inline] __x64_sys_fallocate+0xbd/0x100 fs/open.c:353 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x41/0xc0 arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x63/0xcd The root cause is race condition as below: - since it tries to remount rw filesystem, so that do_remount won't call sb_prepare_remount_readonly to block fallocate, there may be race condition in between remount and fallocate. - in f2fs_remount(), default_options() will reset mount option to default one, and then update it based on result of parse_options(), so there is a hole which race condition can happen. Thread A Thread B - f2fs_fill_super - parse_options - clear_opt(READ_EXTENT_CACHE) - f2fs_remount - default_options - set_opt(READ_EXTENT_CACHE) - f2fs_fallocate - f2fs_insert_range - f2fs_drop_extent_tree - __drop_extent_tree - __may_extent_tree - test_opt(READ_EXTENT_CACHE) return true - write_lock(&et->lock) access NULL pointer - parse_options - clear_opt(READ_EXTENT_CACHE)
Source: CVE Program / CVE List V5
CVSS Information
N/A
Source: CVE Program / CVE List V5
Vulnerability Type
N/A
Source: CVE Program / CVE List V5
Vulnerability Title
Linux kernel 安全漏洞
Source: CNNVD (China National Vulnerability Database)
Vulnerability Description
Linux kernel是美国Linux基金会的开源操作系统Linux所使用的内核。 Linux kernel存在安全漏洞,该漏洞源于f2fs_remount函数中重置不可更改的挂载选项,可能导致一般保护错误。
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

Vendor Product Affected Versions CPE Subscribe
Linux Linux 98e4da8ca301e062d79ae168c67e56f3c3de3ce4 ~ 115557cc226a927924f2d7d1980ccbf6e3b3bb36 -
Linux Linux 3.8 -

II. Public POCs for CVE-2023-53447

# POC Description Source Link Shenlong Link
AI-Generated POC Premium

No public POC found.

Login to generate AI POC

III. Intelligence Information for CVE-2023-53447

请登录查看更多情报信息。

Same Patch Batch · Linux · 2025-09-18 · 121 CVEs total

CVE-2022-50410 9.8 CRITICAL NFSD: Protect against send buffer overflow in NFSv2 READ
CVE-2022-50401 9.8 CRITICAL nfsd: under NFSv4.1, fix double svc_xprt_put on rpc_create failure
CVE-2023-53382 9.8 CRITICAL net/smc: Reset connection when trying to use SMCRv2 fails.
CVE-2022-50419 8.8 HIGH Bluetooth: hci_sysfs: Fix attempting to call device_add multiple times
CVE-2023-53431 8.8 HIGH scsi: ses: Handle enclosure with just a primary component gracefully
CVE-2023-53432 8.8 HIGH firewire: net: fix use after free in fwnet_finish_incoming_packet()
CVE-2022-50386 8.8 HIGH Bluetooth: L2CAP: Fix user-after-free
CVE-2022-50413 8.8 HIGH wifi: mac80211: fix use-after-free
CVE-2023-53374 8.8 HIGH Bluetooth: hci_conn: fail SCO/ISO via hci_conn_failed if ACL gone early
CVE-2023-53372 8.2 HIGH sctp: fix a potential overflow in sctp_ifwdtsn_skip
CVE-2022-50399 7.8 HIGH media: atomisp: prevent integer overflow in sh_css_set_black_frame()
CVE-2023-53429 7.8 HIGH btrfs: don't check PageError in __extent_writepage
CVE-2023-53373 7.8 HIGH crypto: seqiv - Handle EBUSY correctly
CVE-2023-53376 7.8 HIGH scsi: mpi3mr: Use number of bits to manage bitmap sizes
CVE-2023-53386 7.8 HIGH Bluetooth: Fix potential use-after-free when clear keys
CVE-2022-50417 7.8 HIGH drm/panfrost: Fix GEM handle creation ref-counting
CVE-2023-53394 7.8 HIGH net/mlx5e: xsk: Fix crash on regular rq reactivation
CVE-2023-53387 7.8 HIGH scsi: ufs: core: Fix device management cmd timeout flow
CVE-2023-53388 7.8 HIGH drm/mediatek: Clean dangling pointer on bind error path
CVE-2023-53378 7.8 HIGH drm/i915/dpt: Treat the DPT BO as a framebuffer

Showing top 20 of 121 CVEs. View all on vendor page &rarr; →

IV. Related Vulnerabilities

V. Comments for CVE-2023-53447

No comments yet


Leave a comment