CVE-2024-26869: f2fs: fix to truncate meta inode pages forcely

Severity: medium (CVSS 4.7 v3.1)
Exploited in the wild: not listed in CISA KEV
EPSS: 0.2% probability of exploitation in the next 30 days
Public exploit or detection template: none known
Published: 2024-04-17 · updated 2026-10-30
Weakness: CWE-362

Description

In the Linux kernel, the following vulnerability has been resolved: f2fs: fix to truncate meta inode pages forcely Below race case can cause data corruption: Thread A GC thread - gc_data_segment - ra_data_block - locked meta_inode page - f2fs_inplace_write_data - invalidate_mapping_pages : fail to invalidate meta_inode page due to lock failure or dirty|writeback status - f2fs_submit_page_bio : write last dirty data to old blkaddr - move_data_block - load old data from meta_inode page - f2fs_submit_page_write : write old data to new blkaddr Because invalidate_mapping_pages() will skip invalidating page which has unclear status including locked, dirty, writeback and so on, so we need to use truncate_inode_pages_range() instead of invalidate_mapping_pages() to make sure meta_inode page will be dropped.

Affected products

Linux kernel: from 4.19 before 6.6.23; from 6.7 before 6.7.11; from 6.8 before 6.8.2 — fixed in 6.6.23, 6.7.11, 6.8.2
Linux: 4.19 — fixed in 6.9

How to fix

Upgrade to a fixed version: Linux kernel 6.6.23, 6.7.11, 6.8.2; Linux 6.9. Check the vendor advisory for mitigations.

References

Get alerted when CVE-2024-26869 or the next vulnerability affects your stack