CVE-2026-93235f2fs: fix to zero post-EOF data when extending file size
- —Not scoredno CVSS score yet
- 0.21%Exploitation in 30 daysEPSS · top 89% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
Description
In the Linux kernel, the following vulnerability has been resolved: f2fs: fix to zero post-EOF data when extending file size generic/794 4s ... - output mismatch (see /share/git/fstests/results//generic/794.out.bad) --- tests/generic/794.out 2026-06-12 08:46:32.766426241 +0800 +++ /share/git/fstests/results//generic/794.out.bad 2026-07-05 18:32:55.000000000 +0800 @@ -1,4 +1,16 @@ QA output created by 794 append_write +FAIL: non-zero data in gap [4080,4096) after shutdown+remount +000000 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a >ZZZZZZZZZZZZZZZZ< +* +001000 truncate_up ... (Run 'diff -u /share/git/fstests/tests/generic/794.out /share/git/fstests/results//generic/794.out.bad' to see the entire diff) Ran: generic/794 Failures: generic/794 Failed 1 of 1 tests Steps of generic/794: 1. write 4096 bytes to file w/ 0x5a 2. use fiemap to get PBA of first block in file 3. truncate file to 4080 4. umount; write 4096 bytes to file w/ 0x5a directly via PBA; mount 5. extend filesize via a) append 4096 from offset 4096, or b) truncate 8192, or c) fallocate 4096 from offset 4096 6. verify the gap is zeroed in memory [4080,4096) 7. sync range 4096 from offset 4096; shutdown -f (flush meta before shutdown) 8. umount; mount; verify [4080,4096) is zeroed or not. When extending file size (e.g. via truncate, fallocate, or write) across an unaligned EOF boundary, we need to ensure that post-EOF data in the partial page is zeroed out in pagecache and marked dirty, then writeback the cache to persist zeroed data before committing inode w/ updated i_size. This help to prevent stale disk data beyond the previous EOF from being exposed after remounting or crash recovery. Since f2fs is a LFS filesystem, we only support direct write via PBA in pinfile, and pinfile has section-aligned filesize, so in Android, there should no problem, but for other usage in different environment, let's fix this w/ fsync_mode=strict mount option.
Timeline
ID reserved
By Linux
- 7 days later
· 7 days later
Published
- 25 days later
· 25 days later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.
- EPSS (exploitation in 30 days)
- 0.21% · top 89% of all CVEs (17 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.
Affected products
- affected fbfa2cc58d5363f780f4f2ad0243a47185c2bb2a – < 6882d458d2e403f6ba7b45542dd31a6b7531eb2e
- affected fbfa2cc58d5363f780f4f2ad0243a47185c2bb2a – < 32c7f11a24268ba8d3bb50ea7f54d33f698cd253
- affected fbfa2cc58d5363f780f4f2ad0243a47185c2bb2a – < 91ec55ddc097ccddd25ffb95a3d079b2ef362372
- affected fbfa2cc58d5363f780f4f2ad0243a47185c2bb2a – < c42608c09b6b5d5967bf211c255914c068c2cde1
- affected fbfa2cc58d5363f780f4f2ad0243a47185c2bb2a – < 5eced87b7d19dbc76ebdddaf322046f9ac582fcb
- affected 3.8
- unaffected < 3.8
- unaffected 6.6.157 – ≤ 6.6.*
- unaffected 6.12.110 – ≤ 6.12.*
- unaffected 6.18.51 – ≤ 6.18.*
- unaffected 7.2.5 – ≤ 7.2.*
- unaffected 7.3 – ≤ *
References
References5
- https://git.kernel.org/stable/c/6882d458d2e403f6ba7b45542dd31a6b7531eb2e (opens in a new tab)
- https://git.kernel.org/stable/c/32c7f11a24268ba8d3bb50ea7f54d33f698cd253 (opens in a new tab)
- https://git.kernel.org/stable/c/91ec55ddc097ccddd25ffb95a3d079b2ef362372 (opens in a new tab)
- https://git.kernel.org/stable/c/c42608c09b6b5d5967bf211c255914c068c2cde1 (opens in a new tab)
- https://git.kernel.org/stable/c/5eced87b7d19dbc76ebdddaf322046f9ac582fcb (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-86240 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-93235)Record last updated .