CVE-2026-89829
HighCVSS 7.8Exploitation Probability (EPSS)
Low risk6th percentile - higher than 6% of all known CVEs
Summary
In the Linux kernel, f2fs_sanity_check_node_footer() is not passed the correct folio->index value, causing it to check the same nid incorrectly. This can lead to improper node consistency verification in the f2fs filesystem.
Risk Assessment
Incorrect verification may cause metadata corruption in f2fs to be missed or misreported, threatening data integrity.
Recommendation
Update the Linux kernel to a version with the fix that passes folio->index to f2fs_sanity_check_node_footer().
Other vulnerabilities in Linux kernel (f2fs)
See all- CVE-2026-93235Low risk· EPSS 10%
A flaw was found in the Linux kernel F2FS filesystem where extending a file size across an unaligned EOF boundary did not zero out post-EOF data in the partial page. As a result, stale disk data beyond the previous EOF could be exposed after remounting or crash recovery.
- CVE-2026-89830Low risk· EPSS 10%
In the Linux kernel, __allocate_data_block() in the f2fs filesystem increments the valid block count via inc_valid_block_count() when allocating a new data block, but if the subsequent f2fs_allocate_data_block() fails, the function returns the error without rolling back that increment. This causes a permanent valid block count leak.
- CVE-2024-56692High
In the Linux kernel, the f2fs filesystem lacked a sanity check on the node block address (blkaddr) in truncate_node(). On a crafted filesystem image, a corrupted NAT entry can cause a kernel panic during block invalidation.
Original NVD description (English source)
In the Linux kernel, the following vulnerability has been resolved: f2fs: fix to pass folio->index to f2fs_sanity_check_node_footer() Otherwise in f2fs_sanity_check_node_footer(), it will check the same nid incorrectly.
Vulnerability data from NVD (NIST) · CISA KEV · EPSS