Filesystem corruption via stale parent directory entry
Published Feb 22, 2024 · Updated Aug 5, 2026
Directory-entry corruption in Linux allows local users to corrupt F2FS metadata through a cross-directory whiteout rename. In f2fs_rename(), the whiteout path skips f2fs_set_link(), leaving the moved directory's '..' entry pointing to its former parent. Ordinary write and rename permission on an already-mounted F2FS volume is enough; the persistent inconsistency can expose unrelated directories, fail filesystem checks, or require repair or a wipe.
Summary
What happened
Directory-entry corruption in Linux allows local users to corrupt F2FS metadata through a cross-directory whiteout rename. In f2fs_rename(), the whiteout path skips f2fs_set_link(), leaving the moved directory's '..' entry pointing to its former parent. Ordinary write and rename permission on an already-mounted F2FS volume is enough; the persistent inconsistency can expose unrelated directories, fail filesystem checks, or require repair or a wipe.
The record
- CVE
- CVE-2023-52444
- Published
- Feb 22, 2024
- Updated
- Aug 5, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- T1565.001
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Feb 22, 2024CVE publishedPublication date reported by the CVE source.
- Aug 5, 2026Record 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=4.2
- Affected versionversion=7e01e7ad746bc8198a8b46163ddc73a1c7d22339 <02160112e6d45c2610b049df6eb693d7a2e57b46
- Affected versionversion=7e01e7ad746bc8198a8b46163ddc73a1c7d22339 <2fb4867f4405aea8c0519d7d188207f232a57862
- Affected versionversion=7e01e7ad746bc8198a8b46163ddc73a1c7d22339 <53edb549565f55ccd0bdf43be3d66ce4c2d48b28
- Affected versionversion=7e01e7ad746bc8198a8b46163ddc73a1c7d22339 <5624a3c1b1ebc8991318e1cce2aa719542991024
- Affected versionversion=7e01e7ad746bc8198a8b46163ddc73a1c7d22339 <6f866885e147d33efc497f1095f35b2ee5ec7310
- Affected versionversion=7e01e7ad746bc8198a8b46163ddc73a1c7d22339 <d3c0b49aaa12a61d560528f5d605029ab57f0728
- Affected versionversion=7e01e7ad746bc8198a8b46163ddc73a1c7d22339 <f0145860c20be6bae6785c7a2249577674702ac7
- Affected versionversion=7e01e7ad746bc8198a8b46163ddc73a1c7d22339 <f100ba617d8be6c98a68f3744ef7617082975b77
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