CVE-2023-54187
Description
In the Linux kernel, the following vulnerability has been resolved:
f2fs: fix potential corruption when moving a directory
F2FS has the same issue in ext4_rename causing crash revealed by xfstests/generic/707.
See also commit 0813299c586b ("ext4: Fix possible corruption when moving a directory")
AI Insight
LLM-synthesized narrative grounded in this CVE's description and references.
A race condition in the Linux kernel's F2FS filesystem can corrupt directories during rename operations, mirroring a known ext4 bug.
Vulnerability
Description
CVE-2023-54187 is a race condition vulnerability in the Linux kernel's F2FS (Flash-Friendly File System) implementation. The bug occurs during directory rename operations, where a race between concurrent rename and other directory operations can lead to filesystem corruption. This issue is analogous to a previously fixed vulnerability in ext4 (CVE-2023-54187 is the F2FS counterpart of the ext4 bug addressed by commit 0813299c586b) [1].
Exploitation
An attacker with local access and the ability to trigger concurrent rename operations on a directory can exploit this race condition. The attack requires no special privileges beyond the ability to perform file operations on the F2FS filesystem. The race window exists when the kernel's VFS layer of directory entry manipulation is not properly serialized, allowing a rename to proceed while another operation modifies the same directory structure [2].
Impact
Successful exploitation can cause directory corruption, potentially leading to data loss or filesystem inconsistency. In the worst case, this could result in a denial of service or, if the corruption affects critical system directories, a system crash the system. The vulnerability is rated with a CVSS score of 5.5 (Medium), indicating a moderate severity due to the requirement for local access and the potential for data integrity impact [3].
Mitigation
The fix has been included in the Linux kernel stable releases. Users should update their kernel to a version containing the commit that addresses this issue. The patch ensures proper locking during directory rename operations, preventing the race condition. No workaround is available other than applying the kernel update [1][2][3].
AI Insight generated on May 19, 2026. Synthesized from this CVE's description and the cited reference URLs; citations are validated against the source bundle.
Affected products
2Patches
73e7703624612957904f531fd8f57f3e112cf8a0b544b7caef201911009520a76082a4a32d94772154e52Vulnerability mechanics
Generated on May 9, 2026. Inputs: CWE entries + fix-commit diffs from this CVE's patches. Citations validated against bundle.
References
7- git.kernel.org/stable/c/0a76082a4a32a90d1ef33dee8b400efc082b4b6fnvd
- git.kernel.org/stable/c/3e77036246123ff710fa2661dcaa12a45284f09bnvd
- git.kernel.org/stable/c/8a0b544b7caedfbc05065b6377fd1d8bf7ef5e70nvd
- git.kernel.org/stable/c/8f57f3e112cf1d16682b6ff9c31c72f40f7da9c9nvd
- git.kernel.org/stable/c/957904f531fd857a92743b11fbc9c9ffdf7f3207nvd
- git.kernel.org/stable/c/d94772154e524b329a168678836745d2773a6e02nvd
- git.kernel.org/stable/c/f20191100952013f0916418cdaed0ab55c7b634cnvd
News mentions
0No linked articles in our index yet.