{"api_version":"1","generated_at":"2026-09-24T18:33:08+00:00","cve":"CVE-2026-93235","urls":{"html":"https://cve.report/CVE-2026-93235","api":"https://cve.report/api/cve/CVE-2026-93235.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2026-93235","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2026-93235"},"summary":{"title":"f2fs: fix to zero post-EOF data when extending file size","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nf2fs: fix to zero post-EOF data when extending file size\n\ngeneric/794  4s ... - output mismatch (see /share/git/fstests/results//generic/794.out.bad)\n    --- tests/generic/794.out   2026-06-12 08:46:32.766426241 +0800\n    +++ /share/git/fstests/results//generic/794.out.bad 2026-07-05 18:32:55.000000000 +0800\n    @@ -1,4 +1,16 @@\n     QA output created by 794\n     append_write\n    +FAIL: non-zero data in gap [4080,4096) after shutdown+remount\n    +000000 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a  >ZZZZZZZZZZZZZZZZ<\n    +*\n    +001000\n     truncate_up\n    ...\n    (Run 'diff -u /share/git/fstests/tests/generic/794.out /share/git/fstests/results//generic/794.out.bad'  to see the entire diff)\nRan: generic/794\nFailures: generic/794\nFailed 1 of 1 tests\n\nSteps of generic/794:\n1. write 4096 bytes to file w/ 0x5a\n2. use fiemap to get PBA of first block in file\n3. truncate file to 4080\n4. umount; write 4096 bytes to file w/ 0x5a directly via PBA; mount\n5. extend filesize via\n   a) append 4096 from offset 4096, or\n   b) truncate 8192, or\n   c) fallocate 4096 from offset 4096\n6. verify the gap is zeroed in memory [4080,4096)\n7. sync range 4096 from offset 4096; shutdown -f (flush meta before shutdown)\n8. umount; mount; verify [4080,4096) is zeroed or not.\n\nWhen extending file size (e.g. via truncate, fallocate, or write) across an\nunaligned EOF boundary, we need to ensure that post-EOF data in the partial\npage is zeroed out in pagecache and marked dirty, then writeback the cache to\npersist zeroed data before committing inode w/ updated i_size.\n\nThis help to prevent stale disk data beyond the previous EOF from being exposed\nafter remounting or crash recovery.\n\nSince f2fs is a LFS filesystem, we only support direct write via PBA in pinfile,\nand pinfile has section-aligned filesize, so in Android, there should no problem,\nbut for other usage in different environment, let's fix this w/ fsync_mode=strict\nmount option.","state":"PUBLISHED","assigner":"Linux","published_at":"2026-09-24 16:17:19","updated_at":"2026-09-24 16:17:19"},"problem_types":[],"metrics":[],"references":[{"url":"https://git.kernel.org/stable/c/6882d458d2e403f6ba7b45542dd31a6b7531eb2e","name":"https://git.kernel.org/stable/c/6882d458d2e403f6ba7b45542dd31a6b7531eb2e","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/c42608c09b6b5d5967bf211c255914c068c2cde1","name":"https://git.kernel.org/stable/c/c42608c09b6b5d5967bf211c255914c068c2cde1","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/5eced87b7d19dbc76ebdddaf322046f9ac582fcb","name":"https://git.kernel.org/stable/c/5eced87b7d19dbc76ebdddaf322046f9ac582fcb","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/91ec55ddc097ccddd25ffb95a3d079b2ef362372","name":"https://git.kernel.org/stable/c/91ec55ddc097ccddd25ffb95a3d079b2ef362372","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/32c7f11a24268ba8d3bb50ea7f54d33f698cd253","name":"https://git.kernel.org/stable/c/32c7f11a24268ba8d3bb50ea7f54d33f698cd253","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-93235","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-93235","name":"NVD vulnerability detail","refsource":"NVD","tags":["canonical","analysis"]}],"affected":[{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 6882d458d2e403f6ba7b45542dd31a6b7531eb2e git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 32c7f11a24268ba8d3bb50ea7f54d33f698cd253 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 91ec55ddc097ccddd25ffb95a3d079b2ef362372 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 c42608c09b6b5d5967bf211c255914c068c2cde1 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 5eced87b7d19dbc76ebdddaf322046f9ac582fcb git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 6.6.157 semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 6.12.110 semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 6.18.51 semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 7.2.5 semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.6.157 6.6.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.12.110 6.12.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.18.51 6.18.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.2.5 7.2.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.3-rc1 * original_commit_for_fix","platforms":[]}],"timeline":[],"solutions":[],"workarounds":[],"exploits":[],"credits":[],"nvd_cpes":[],"vendor_comments":[],"enrichments":{"kev":null,"epss":null,"legacy_qids":[]},"source_records":{"cve_program":{"containers":{"cna":{"affected":[{"defaultStatus":"unaffected","product":"Linux","programFiles":["fs/f2fs/file.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"lessThan":"6882d458d2e403f6ba7b45542dd31a6b7531eb2e","status":"affected","version":"1da177e4c3f41524e886b7f1b8a0c1fc7321cac2","versionType":"git"},{"lessThan":"32c7f11a24268ba8d3bb50ea7f54d33f698cd253","status":"affected","version":"1da177e4c3f41524e886b7f1b8a0c1fc7321cac2","versionType":"git"},{"lessThan":"91ec55ddc097ccddd25ffb95a3d079b2ef362372","status":"affected","version":"1da177e4c3f41524e886b7f1b8a0c1fc7321cac2","versionType":"git"},{"lessThan":"c42608c09b6b5d5967bf211c255914c068c2cde1","status":"affected","version":"1da177e4c3f41524e886b7f1b8a0c1fc7321cac2","versionType":"git"},{"lessThan":"5eced87b7d19dbc76ebdddaf322046f9ac582fcb","status":"affected","version":"1da177e4c3f41524e886b7f1b8a0c1fc7321cac2","versionType":"git"},{"lessThan":"6.6.157","status":"affected","version":"0","versionType":"semver"},{"lessThan":"6.12.110","status":"affected","version":"0","versionType":"semver"},{"lessThan":"6.18.51","status":"affected","version":"0","versionType":"semver"},{"lessThan":"7.2.5","status":"affected","version":"0","versionType":"semver"}]},{"defaultStatus":"affected","product":"Linux","programFiles":["fs/f2fs/file.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"lessThanOrEqual":"6.6.*","status":"unaffected","version":"6.6.157","versionType":"semver"},{"lessThanOrEqual":"6.12.*","status":"unaffected","version":"6.12.110","versionType":"semver"},{"lessThanOrEqual":"6.18.*","status":"unaffected","version":"6.18.51","versionType":"semver"},{"lessThanOrEqual":"7.2.*","status":"unaffected","version":"7.2.5","versionType":"semver"},{"lessThanOrEqual":"*","status":"unaffected","version":"7.3-rc1","versionType":"original_commit_for_fix"}]}],"cpeApplicability":[{"nodes":[{"cpeMatch":[{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"6.6.157","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"6.12.110","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"6.18.51","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.2.5","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.3-rc1","vulnerable":true}],"negate":false,"operator":"OR"}]}],"descriptions":[{"lang":"en","value":"In the Linux kernel, the following vulnerability has been resolved:\n\nf2fs: fix to zero post-EOF data when extending file size\n\ngeneric/794  4s ... - output mismatch (see /share/git/fstests/results//generic/794.out.bad)\n    --- tests/generic/794.out   2026-06-12 08:46:32.766426241 +0800\n    +++ /share/git/fstests/results//generic/794.out.bad 2026-07-05 18:32:55.000000000 +0800\n    @@ -1,4 +1,16 @@\n     QA output created by 794\n     append_write\n    +FAIL: non-zero data in gap [4080,4096) after shutdown+remount\n    +000000 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a  >ZZZZZZZZZZZZZZZZ<\n    +*\n    +001000\n     truncate_up\n    ...\n    (Run 'diff -u /share/git/fstests/tests/generic/794.out /share/git/fstests/results//generic/794.out.bad'  to see the entire diff)\nRan: generic/794\nFailures: generic/794\nFailed 1 of 1 tests\n\nSteps of generic/794:\n1. write 4096 bytes to file w/ 0x5a\n2. use fiemap to get PBA of first block in file\n3. truncate file to 4080\n4. umount; write 4096 bytes to file w/ 0x5a directly via PBA; mount\n5. extend filesize via\n   a) append 4096 from offset 4096, or\n   b) truncate 8192, or\n   c) fallocate 4096 from offset 4096\n6. verify the gap is zeroed in memory [4080,4096)\n7. sync range 4096 from offset 4096; shutdown -f (flush meta before shutdown)\n8. umount; mount; verify [4080,4096) is zeroed or not.\n\nWhen extending file size (e.g. via truncate, fallocate, or write) across an\nunaligned EOF boundary, we need to ensure that post-EOF data in the partial\npage is zeroed out in pagecache and marked dirty, then writeback the cache to\npersist zeroed data before committing inode w/ updated i_size.\n\nThis help to prevent stale disk data beyond the previous EOF from being exposed\nafter remounting or crash recovery.\n\nSince f2fs is a LFS filesystem, we only support direct write via PBA in pinfile,\nand pinfile has section-aligned filesize, so in Android, there should no problem,\nbut for other usage in different environment, let's fix this w/ fsync_mode=strict\nmount option."}],"providerMetadata":{"dateUpdated":"2026-09-24T15:33:33.241Z","orgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","shortName":"Linux"},"references":[{"url":"https://git.kernel.org/stable/c/6882d458d2e403f6ba7b45542dd31a6b7531eb2e"},{"url":"https://git.kernel.org/stable/c/32c7f11a24268ba8d3bb50ea7f54d33f698cd253"},{"url":"https://git.kernel.org/stable/c/91ec55ddc097ccddd25ffb95a3d079b2ef362372"},{"url":"https://git.kernel.org/stable/c/c42608c09b6b5d5967bf211c255914c068c2cde1"},{"url":"https://git.kernel.org/stable/c/5eced87b7d19dbc76ebdddaf322046f9ac582fcb"}],"title":"f2fs: fix to zero post-EOF data when extending file size","x_generator":{"engine":"bippy-1.2.0"}}},"cveMetadata":{"assignerOrgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","assignerShortName":"Linux","cveId":"CVE-2026-93235","datePublished":"2026-09-24T15:33:33.241Z","dateReserved":"2026-09-17T16:02:15.095Z","dateUpdated":"2026-09-24T15:33:33.241Z","state":"PUBLISHED"},"dataType":"CVE_RECORD","dataVersion":"5.2"},"nvd":{"publishedDate":"2026-09-24 16:17:19","lastModifiedDate":"2026-09-24 16:17:19","problem_types":[],"metrics":[],"configurations":[]},"legacy_mitre":{"record":{"CveYear":"2026","CveId":"93235","Ordinal":"1","Title":"f2fs: fix to zero post-EOF data when extending file size","CVE":"CVE-2026-93235","Year":"2026"},"notes":[{"CveYear":"2026","CveId":"93235","Ordinal":"1","NoteData":"In the Linux kernel, the following vulnerability has been resolved:\n\nf2fs: fix to zero post-EOF data when extending file size\n\ngeneric/794  4s ... - output mismatch (see /share/git/fstests/results//generic/794.out.bad)\n    --- tests/generic/794.out   2026-06-12 08:46:32.766426241 +0800\n    +++ /share/git/fstests/results//generic/794.out.bad 2026-07-05 18:32:55.000000000 +0800\n    @@ -1,4 +1,16 @@\n     QA output created by 794\n     append_write\n    +FAIL: non-zero data in gap [4080,4096) after shutdown+remount\n    +000000 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a  >ZZZZZZZZZZZZZZZZ<\n    +*\n    +001000\n     truncate_up\n    ...\n    (Run 'diff -u /share/git/fstests/tests/generic/794.out /share/git/fstests/results//generic/794.out.bad'  to see the entire diff)\nRan: generic/794\nFailures: generic/794\nFailed 1 of 1 tests\n\nSteps of generic/794:\n1. write 4096 bytes to file w/ 0x5a\n2. use fiemap to get PBA of first block in file\n3. truncate file to 4080\n4. umount; write 4096 bytes to file w/ 0x5a directly via PBA; mount\n5. extend filesize via\n   a) append 4096 from offset 4096, or\n   b) truncate 8192, or\n   c) fallocate 4096 from offset 4096\n6. verify the gap is zeroed in memory [4080,4096)\n7. sync range 4096 from offset 4096; shutdown -f (flush meta before shutdown)\n8. umount; mount; verify [4080,4096) is zeroed or not.\n\nWhen extending file size (e.g. via truncate, fallocate, or write) across an\nunaligned EOF boundary, we need to ensure that post-EOF data in the partial\npage is zeroed out in pagecache and marked dirty, then writeback the cache to\npersist zeroed data before committing inode w/ updated i_size.\n\nThis help to prevent stale disk data beyond the previous EOF from being exposed\nafter remounting or crash recovery.\n\nSince f2fs is a LFS filesystem, we only support direct write via PBA in pinfile,\nand pinfile has section-aligned filesize, so in Android, there should no problem,\nbut for other usage in different environment, let's fix this w/ fsync_mode=strict\nmount option.","Type":"Description","Title":"f2fs: fix to zero post-EOF data when extending file size"}]}}}