The Linux kernel f2fs filesystem had a vulnerability where non-inode dnodes could be misparsed as inodes due to identical footer inode and node IDs. This caused incorrect block address calculations in f2fs_truncate_hole(), potentially triggering a kernel panic. The root cause was that the existing sanity checks did not differentiate non-inode dnodes properly, allowing corrupted or malformed nodes to cause system instability. The fix introduced a new node type NODE_TYPE_NON_INODE and updated sanity_check_node_footer() to validate node footers correctly, preventing the misinterpretation and associated panic.

Exploitation of this vulnerability can lead to a kernel panic, causing denial of service on affected systems running the vulnerable Linux kernel with f2fs filesystem. The impact includes system instability and potential data loss due to unexpected crashes during filesystem operations involving truncation holes. The CVSS vector indicates high confidentiality, integrity, and availability impact, but no known exploits are reported in the wild at this time.

A fix for this vulnerability has been implemented in the Linux kernel. Users should update to a kernel version that includes this patch to prevent the issue. Since no specific patch links or vendor advisories are provided, check the official Linux kernel repositories or distributions for the updated kernel version containing this fix. Until patched, avoid operations that may trigger the vulnerability such as truncation hole operations on f2fs filesystems with potentially corrupted nodes.