Linux Kernel f2fs Incorrect nat_entry Flag Handling Vulnerability

A vulnerability in the Linux kernel's F2FS (Flash-Friendly File System) has been addressed. The issue arose because the function 'f2fs_need_dentry_mark()' accessed nat_entry flags without proper synchronization with the checkpoint process. This lack of mutual exclusion could lead to an incorrect marking state for inode blocks. The problem was identified when a file was created, written, and synchronized, followed by a checkpoint write. Although the inode had been checkpointed, it still retained a specific flag indicating it needed a directory entry mark, creating an inconsistency. The vulnerability has been fixed by moving the dentry mark setting into the node writing function and protecting it with a lock to ensure proper synchronization.

Impact

The vulnerability could cause filesystem inconsistencies, where inodes are incorrectly marked as needing updates, potentially leading to data corruption or loss.

Reproduction

To reproduce this vulnerability, create and write a file in an F2FS filesystem, then synchronize it. After writing a checkpoint, the inode should be checked. Despite having been checkpointed, the inode may still show a flag indicating it needs a dentry mark, revealing the inconsistency caused by the improper flag handling.

Remediation

Users can upgrade to the latest stable version of the Linux kernel where this vulnerability has been fixed.