PT-2026-2590 · F2Fs+3 · F2Fs+3
Published
2026-01-13
·
Updated
2026-05-11
·
CVE-2025-71069
None
No severity ratings or metrics are available. When they are, we'll update the corresponding info on the page.
Name of the Vulnerable Software and Affected Versions
Linux kernel (affected versions not specified)
Description
The F2FS filesystem, when mounting filesystems with corrupted directory depth values, can experience issues with dentry cache invalidation during rename operations involving whiteouts. Specifically, if
f2fs add link fails during whiteout creation due to a corrupted directory structure after partial directory modifications have been committed to disk, the VFS does not update the dentry cache. This results in stale mappings where the dentry cache still points to an old inode that has already had its i nlink decremented to zero. Subsequent operations using this stale cache can then incorrectly reference freed inodes, potentially triggering a WARNING in drop nlink() when attempting to decrement the inode link count on an inode that already has a link count of zero. The issue occurs when a first rename operation (RENAME WHITEOUT) partially completes, and a second rename operation targets the same entry, utilizing the stale cache information.Recommendations
At the moment, there is no information about a newer version that contains a fix for this vulnerability.
Exploit
Found an issue in the description? Have something to add? Feel free to write us 👾
Related Identifiers
Affected Products
F2Fs
Linuxmint
Linux Kernel
Ubuntu