CVE-2023-52444: f2fs: fix to avoid dirent corruption

Severity: high (CVSS 7.8 v3.1)
Exploited in the wild: not listed in CISA KEV
EPSS: 0.2% probability of exploitation in the next 30 days
Public exploit or detection template: none known
Published: 2024-02-22 · updated 2026-10-15
Weakness: CWE-119

Description

In the Linux kernel, the following vulnerability has been resolved: f2fs: fix to avoid dirent corruption As Al reported in link[1]: f2fs_rename() ... if (old_dir != new_dir && !whiteout) f2fs_set_link(old_inode, old_dir_entry, old_dir_page, new_dir); else f2fs_put_page(old_dir_page, 0); You want correct inumber in the ".." link. And cross-directory rename does move the source to new parent, even if you'd been asked to leave a whiteout in the old place. [1] https://lore.kernel.org/all/20231017055040.GN800259@ZenIV/ With below testcase, it may cause dirent corruption, due to it missed to call f2fs_set_link() to update ".." link to new directory. - mkdir -p dir/foo - renameat2 -w dir/foo bar [ASSERT] (__chk_dots_dentries:1421) --> Bad inode number[0x4] for '..', parent parent ino is [0x3] [FSCK] other corrupted bugs [Fail]

Affected products

Linux kernel: from 4.2.0 before 4.19.306; from 4.20 before 5.4.268; from 5.5.0 before 5.10.209; from 5.11.0 before 5.15.148; from 5.16.0 before 6.1.75; from 6.2.0 before 6.6.14 — fixed in 4.19.306, 5.10.209, 5.15.148, 5.4.268, 6.1.75, 6.6.14

How to fix

Upgrade to a fixed version: Linux kernel 4.19.306, 5.10.209, 5.15.148, 5.4.268. Check the vendor advisory for mitigations.

References

Get alerted when CVE-2023-52444 or the next vulnerability affects your stack