CyberRota Analysis
AI-GeneratedThe vulnerability affects the Linux kernel's f2fs filesystem, specifically in the handling of orphan inode entries during recovery from checkpoint data. An attacker can exploit this flaw by crafting a malicious image that leads to kernel panic, potentially causing system instability and data loss. Organizations using Linux systems with f2fs should prioritize patching to mitigate this high-severity risk.
Original NVD Description
In the Linux kernel, the following vulnerability has been resolved: f2fs: validate orphan inode entry count f2fs_recover_orphan_inodes() trusts the orphan block entry_count when replaying orphan inodes from the checkpoint pack. A corrupted entry_count larger than F2FS_ORPHANS_PER_BLOCK makes the recovery loop read past the ino[] array and interpret footer or following data as inode numbers. On a crafted image, mounting an unpatched kernel can drive orphan recovery into f2fs_bug_on() and panic the kernel. Validate entry_count before consuming entries so corrupted checkpoint data fails the mount with -EFSCORRUPTED and requests fsck instead. Set ERROR_INCONSISTENT_ORPHAN as well, so the corruption reason can be recorded in the superblock s_errors[] field. This gives fsck a persistent hint even though mount-time orphan recovery failure may leave no chance to persist SBI_NEED_FSCK through a checkpoint.