{"id":"CVE-2024-26869","state":"PUBLISHED","title":"f2fs: fix to truncate meta inode pages forcely","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nf2fs: fix to truncate meta inode pages forcely\n\nBelow race case can cause data corruption:\n\nThread A\t\t\t\tGC thread\n\t\t\t\t\t- gc_data_segment\n\t\t\t\t\t - ra_data_block\n\t\t\t\t\t  - locked meta_inode page\n- f2fs_inplace_write_data\n - invalidate_mapping_pages\n : fail to invalidate meta_inode page\n   due to lock failure or dirty|writeback\n   status\n - f2fs_submit_page_bio\n : write last dirty data to old blkaddr\n\t\t\t\t\t - move_data_block\n\t\t\t\t\t  - load old data from meta_inode page\n\t\t\t\t\t  - f2fs_submit_page_write\n\t\t\t\t\t  : write old data to new blkaddr\n\nBecause invalidate_mapping_pages() will skip invalidating page which\nhas unclear status including locked, dirty, writeback and so on, so\nwe need to use truncate_inode_pages_range() instead of\ninvalidate_mapping_pages() to make sure meta_inode page will be dropped.","publishedAt":"2024-04-17T10:27:30.100Z","updatedAt":"2026-10-30T12:17:55.855Z","severity":{"score":7.8,"label":"High","version":"3.1","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","source":"Linux"},"assigner":"Linux","products":["Linux Linux"],"affected":[{"vendor":"Linux","product":"Linux","defaultStatus":"unaffected","versions":[{"version":"6aa58d8ad20a3323f42274c25820a6f54192422d","status":"affected","lessThan":"0721a4f85d12a364002a9476c84b930fbc993f83","versionType":"git"},{"version":"6aa58d8ad20a3323f42274c25820a6f54192422d","status":"affected","lessThan":"c92f2927df860a60ba815d3ee610a944b92a8694","versionType":"git"},{"version":"6aa58d8ad20a3323f42274c25820a6f54192422d","status":"affected","lessThan":"77bfdb89cc222fc7bfe198eda77bdc427d5ac189","versionType":"git"},{"version":"6aa58d8ad20a3323f42274c25820a6f54192422d","status":"affected","lessThan":"04226d8e3c4028dc451e9d8777356ec0f7919253","versionType":"git"},{"version":"6aa58d8ad20a3323f42274c25820a6f54192422d","status":"affected","lessThan":"9f0c4a46be1fe9b97dbe66d49204c1371e3ece65","versionType":"git"}],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","programFiles":["fs/f2fs/checkpoint.c","fs/f2fs/f2fs.h","fs/f2fs/segment.c","include/linux/f2fs_fs.h"]},{"vendor":"Linux","product":"Linux","defaultStatus":"affected","versions":[{"version":"4.19","status":"affected"},{"version":"0","status":"unaffected","lessThan":"4.19","versionType":"semver"},{"version":"6.1.191","status":"unaffected","lessThanOrEqual":"6.1.*","versionType":"semver"},{"version":"6.6.23","status":"unaffected","lessThanOrEqual":"6.6.*","versionType":"semver"},{"version":"6.7.11","status":"unaffected","lessThanOrEqual":"6.7.*","versionType":"semver"},{"version":"6.8.2","status":"unaffected","lessThanOrEqual":"6.8.*","versionType":"semver"},{"version":"6.9","status":"unaffected","lessThanOrEqual":"*","versionType":"original_commit_for_fix"}],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","programFiles":["fs/f2fs/checkpoint.c","fs/f2fs/f2fs.h","fs/f2fs/segment.c","include/linux/f2fs_fs.h"]}],"references":["https://git.kernel.org/stable/c/0721a4f85d12a364002a9476c84b930fbc993f83","https://git.kernel.org/stable/c/c92f2927df860a60ba815d3ee610a944b92a8694","https://git.kernel.org/stable/c/77bfdb89cc222fc7bfe198eda77bdc427d5ac189","https://git.kernel.org/stable/c/04226d8e3c4028dc451e9d8777356ec0f7919253","https://git.kernel.org/stable/c/9f0c4a46be1fe9b97dbe66d49204c1371e3ece65"],"weaknesses":[],"ingestedAt":"2026-10-30T12:34:06.950Z","source":{"repository":"CVEProject/cvelistV5","path":"cves/2024/26xxx/CVE-2024-26869.json","commit":"db8103c5921aac81d5d90efcf3745980dafabf49","baselineCommit":"556c9d3a8cd17e218bb8e452ba7cd619a384ff47"},"raw":{"dataType":"CVE_RECORD","dataVersion":"5.2","cveMetadata":{"cveId":"CVE-2024-26869","state":"PUBLISHED","datePublished":"2024-04-17T10:27:30.100Z","dateUpdated":"2026-10-30T12:17:55.855Z","assignerShortName":"Linux","assignerOrgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","dateReserved":"2024-02-19T14:20:24.184Z"},"containers":{"cna":{"title":"f2fs: fix to truncate meta inode pages forcely","descriptions":[{"lang":"en","value":"In the Linux kernel, the following vulnerability has been resolved:\n\nf2fs: fix to truncate meta inode pages forcely\n\nBelow race case can cause data corruption:\n\nThread A\t\t\t\tGC thread\n\t\t\t\t\t- gc_data_segment\n\t\t\t\t\t - ra_data_block\n\t\t\t\t\t  - locked meta_inode page\n- f2fs_inplace_write_data\n - invalidate_mapping_pages\n : fail to invalidate meta_inode page\n   due to lock failure or dirty|writeback\n   status\n - f2fs_submit_page_bio\n : write last dirty data to old blkaddr\n\t\t\t\t\t - move_data_block\n\t\t\t\t\t  - load old data from meta_inode page\n\t\t\t\t\t  - f2fs_submit_page_write\n\t\t\t\t\t  : write old data to new blkaddr\n\nBecause invalidate_mapping_pages() will skip invalidating page which\nhas unclear status including locked, dirty, writeback and so on, so\nwe need to use truncate_inode_pages_range() instead of\ninvalidate_mapping_pages() to make sure meta_inode page will be dropped."}],"affected":[{"vendor":"Linux","product":"Linux","defaultStatus":"unaffected","versions":[{"version":"6aa58d8ad20a3323f42274c25820a6f54192422d","status":"affected","lessThan":"0721a4f85d12a364002a9476c84b930fbc993f83","versionType":"git"},{"version":"6aa58d8ad20a3323f42274c25820a6f54192422d","status":"affected","lessThan":"c92f2927df860a60ba815d3ee610a944b92a8694","versionType":"git"},{"version":"6aa58d8ad20a3323f42274c25820a6f54192422d","status":"affected","lessThan":"77bfdb89cc222fc7bfe198eda77bdc427d5ac189","versionType":"git"},{"version":"6aa58d8ad20a3323f42274c25820a6f54192422d","status":"affected","lessThan":"04226d8e3c4028dc451e9d8777356ec0f7919253","versionType":"git"},{"version":"6aa58d8ad20a3323f42274c25820a6f54192422d","status":"affected","lessThan":"9f0c4a46be1fe9b97dbe66d49204c1371e3ece65","versionType":"git"}],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","programFiles":["fs/f2fs/checkpoint.c","fs/f2fs/f2fs.h","fs/f2fs/segment.c","include/linux/f2fs_fs.h"]},{"vendor":"Linux","product":"Linux","defaultStatus":"affected","versions":[{"version":"4.19","status":"affected"},{"version":"0","status":"unaffected","lessThan":"4.19","versionType":"semver"},{"version":"6.1.191","status":"unaffected","lessThanOrEqual":"6.1.*","versionType":"semver"},{"version":"6.6.23","status":"unaffected","lessThanOrEqual":"6.6.*","versionType":"semver"},{"version":"6.7.11","status":"unaffected","lessThanOrEqual":"6.7.*","versionType":"semver"},{"version":"6.8.2","status":"unaffected","lessThanOrEqual":"6.8.*","versionType":"semver"},{"version":"6.9","status":"unaffected","lessThanOrEqual":"*","versionType":"original_commit_for_fix"}],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","programFiles":["fs/f2fs/checkpoint.c","fs/f2fs/f2fs.h","fs/f2fs/segment.c","include/linux/f2fs_fs.h"]}],"references":[{"url":"https://git.kernel.org/stable/c/0721a4f85d12a364002a9476c84b930fbc993f83"},{"url":"https://git.kernel.org/stable/c/c92f2927df860a60ba815d3ee610a944b92a8694"},{"url":"https://git.kernel.org/stable/c/77bfdb89cc222fc7bfe198eda77bdc427d5ac189"},{"url":"https://git.kernel.org/stable/c/04226d8e3c4028dc451e9d8777356ec0f7919253"},{"url":"https://git.kernel.org/stable/c/9f0c4a46be1fe9b97dbe66d49204c1371e3ece65"}],"metrics":[{"cvssV3_1":{"version":"3.1","vectorString":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","baseScore":7.8,"baseSeverity":"HIGH"},"scenarios":[{"lang":"en","value":"AV:L - The vulnerable paths are entered through ordinary local file operations on a mounted f2fs volume — buffered overwrite with IPU, fdatasync, or O_DIRECT write — with the racing side driven by the in-kernel GC thread. No network or physical access is involved.\nAC:L - The attacker controls the write side outright and can drive the GC side at will by fragmenting/filling the filesystem to keep background and foreground GC continuously active; the invalidation failure window is the full duration of GC's read bio, during which ra_data_block() holds the meta page locked, so the skip is the expected outcome rather than a narrow accident, and the attempt can be repeated indefinitely.\nPR:L - Any unprivileged local user with write access to a file on an f2fs volume can reach both f2fs_inplace_write_data() and the F2FS_GET_BLOCK_DIO path; the CAP_SYS_ADMIN check on f2fs_ioc_gc() is not a barrier because the default background GC thread and f2fs_balance_fs()-triggered foreground GC provide the racing side without any privilege.\nUI:N - The attacker's own process performs the writes and the GC thread runs automatically as a kernel thread; no victim action of any kind is required.\nS:U - The corruption is confined to the f2fs filesystem and kernel managing it, with no crossing into a different security authority such as a hypervisor or IOMMU domain.\nC:H - META_MAPPING is a global cache keyed by physical block address, and f2fs_invalidate_blocks() can likewise fail to evict, so a stale page can outlive the block's reallocation to a different inode — move_data_block() then copies the previous owner's on-disk content into the attacker's file, disclosing another user's data (plaintext for verity/compressed inodes).\nI:H - This is a direct, silent, persistent on-disk data corruption primitive: freshly written data is overwritten with stale contents, and via physical-block reuse an attacker's stale data can be written into another inode's blocks, modifying data outside the attacker's control with no error reported.\nA:H - Corrupted blocks landing in compressed clusters or encrypted directory/dentry blocks produce decompression and directory-parse failures that raise EFSCORRUPTED, set SBI_NEED_FSCK, and trigger f2fs_handle_error() shutdown (panic under errors=panic or CONFIG_F2FS_CHECK_FS), alongside irrecoverable loss of the corrupted file data."}]}],"providerMetadata":{"shortName":"Linux","orgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","dateUpdated":"2026-10-30T12:17:55.855Z"},"cpeApplicability":[{"nodes":[{"operator":"OR","negate":false,"cpeMatch":[{"vulnerable":true,"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionStartIncluding":"4.19","versionEndExcluding":"6.1.191"},{"vulnerable":true,"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionStartIncluding":"4.19","versionEndExcluding":"6.6.23"},{"vulnerable":true,"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionStartIncluding":"4.19","versionEndExcluding":"6.7.11"},{"vulnerable":true,"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionStartIncluding":"4.19","versionEndExcluding":"6.8.2"},{"vulnerable":true,"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionStartIncluding":"4.19","versionEndExcluding":"6.9"}]}]}],"x_generator":{"engine":"bippy-1.2.0"}},"adp":[{"title":"CISA ADP Vulnrichment","metrics":[{"other":{"type":"ssvc","content":{"timestamp":"2024-06-12T17:28:33.962208Z","id":"CVE-2024-26869","options":[{"Exploitation":"none"},{"Automatable":"no"},{"Technical Impact":"total"}],"role":"CISA Coordinator","version":"2.0.3"}}}],"providerMetadata":{"shortName":"CISA-ADP","orgId":"134c704f-9b21-4f2e-91b3-4a467353bcc0","dateUpdated":"2024-06-12T17:31:41.499Z"}},{"title":"CVE Program Container","references":[{"url":"https://git.kernel.org/stable/c/c92f2927df860a60ba815d3ee610a944b92a8694","tags":["x_transferred"]},{"url":"https://git.kernel.org/stable/c/77bfdb89cc222fc7bfe198eda77bdc427d5ac189","tags":["x_transferred"]},{"url":"https://git.kernel.org/stable/c/04226d8e3c4028dc451e9d8777356ec0f7919253","tags":["x_transferred"]},{"url":"https://git.kernel.org/stable/c/9f0c4a46be1fe9b97dbe66d49204c1371e3ece65","tags":["x_transferred"]}],"providerMetadata":{"shortName":"CVE","orgId":"af854a3a-2127-422b-91ae-364da2661108","dateUpdated":"2024-08-02T00:21:04.218Z"}}]}}}