Local data exposure and corruption via rename race
Published Dec 30, 2025 · Updated Dec 30, 2025
Filesystem corruption in the Linux kernel allows local users to expose or overwrite data by racing cross-directory F2FS moves. f2fs_rename reads an old directory entry before locking the moved directory, allowing a concurrent inline-to-normal dentry conversion to invalidate the retained page and redirect later writes. Exploitation requires local write access to two directories on a mounted F2FS filesystem; successful races can disclose disk blocks, corrupt metadata, hang the filesystem, or crash the kernel.
Summary
What happened
Filesystem corruption in the Linux kernel allows local users to expose or overwrite data by racing cross-directory F2FS moves. f2fs_rename reads an old directory entry before locking the moved directory, allowing a concurrent inline-to-normal dentry conversion to invalidate the retained page and redirect later writes. Exploitation requires local write access to two directories on a mounted F2FS filesystem; successful races can disclose disk blocks, corrupt metadata, hang the filesystem, or crash the kernel.
The record
- CVE
- CVE-2023-54187
- Published
- Dec 30, 2025
- Updated
- Dec 30, 2025
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Dec 30, 2025CVE publishedPublication date reported by the CVE source.
- Dec 30, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <0a76082a4a32a90d1ef33dee8b400efc082b4b6f
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <3e77036246123ff710fa2661dcaa12a45284f09b
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <8a0b544b7caedfbc05065b6377fd1d8bf7ef5e70
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <8f57f3e112cf1d16682b6ff9c31c72f40f7da9c9
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <957904f531fd857a92743b11fbc9c9ffdf7f3207
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <d94772154e524b329a168678836745d2773a6e02
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <f20191100952013f0916418cdaed0ab55c7b634c
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo