The vulnerability is caused by an unbalanced call sequence in the f2fs rename routine within the Linux kernel. A call to f2fs_setup_filename() is made during whiteout initialization without a corresponding f2fs_free_filename() cleanup, leading to a memory leak when the kernel renames a file. The leaked memory cannot be reclaimed, causing kernel memory consumption to grow over time and potentially exhausting kernel memory allocation resources, which could degrade system performance or trigger a kernel out‑of‑memory condition. This flaw does not provide a direct path to privilege escalation or data disclosure.

The issue applies to any Linux kernel in which the f2fs filesystem is enabled and the unpatched rename logic is active. The specific kernel versions are not listed; therefore, any system running a kernel containing the unpatched f2fs rename path is potentially exposed.

The EPSS score is not available and the vulnerability is not listed in the CISA KEV catalog. No CVSS value is supplied, but the flaw offers a low to moderate risk profile: the attack vector is limited to a user‑initiated file rename operation. While the bug cannot currently improve privileges, repeated exploitation could lead to a denial‑of‑service condition by exhausting kernel memory over time. No additional threats beyond standard file rename privileges are indicated.