Answer in brief
CVE-2025-40137 records a Unknown severity vulnerability in f2fs: fix to truncate first page in error path of f2fs_truncate(). The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=92dffd01790a5219d234fc83c3ba854f4490b7f4 <3500d7e1ba53f39bdb8a5aa9c2066b2f08e8c92e || >=92dffd01790a5219d234fc83c3ba854f4490b7f4 <83a8e4efea022506a0e049e7206bdf8be9f78148 || >=92dffd01790a5219d234fc83c3ba854f4490b7f4 <a7b7ebdd7045a36454b3e388a2ecf50344fad9e6 || >=92dffd01790a5219d234fc83c3ba854f4490b7f4 <3b0c8908faa18cded84d64822882a830ab1f4d26 || >=92dffd01790a5219d234fc83c3ba854f4490b7f4 <9251a9e6e871cb03c4714a18efa8f5d4a8818450 | 3500d7e1ba53f39bdb8a5aa9c2066b2f08e8c92e, 83a8e4efea022506a0e049e7206bdf8be9f78148, a7b7ebdd7045a36454b3e388a2ecf50344fad9e6, 3b0c8908faa18cded84d64822882a830ab1f4d26, 9251a9e6e871cb03c4714a18efa8f5d4a8818450 |
| Linux/Linuxgeneric | 3.19 | Not reported |
Published upstream
Nov 12, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Oct 30, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Oct 28, 2026
In the Linux kernel, the following vulnerability has been resolved: f2fs: fix to truncate first page in error path of f2fs_truncate() syzbot reports a bug as below: loop0: detected capacity change from 0 to 40427 F2FS-fs (loop0): Wrong SSA boundary, start(3584) end(4096) blocks(3072) F2FS-fs (loop0): Can't find valid F2FS filesystem in 1th superblock F2FS-fs (loop0): invalid crc value F2FS-fs (loop0): f2fs_convert_inline_folio: corrupted inline inode ino=3, i_addr[0]:0x1601, run fsck to fix. ------------[ cut here ]------------ kernel BUG at fs/inode.c:753! RIP: 0010:clear_inode+0x169/0x190 fs/inode.c:753 Call Trace: <TASK> evict+0x504/0x9c0 fs/inode.c:810 f2fs_fill_super+0x5612/0x6fa0 fs/f2fs/super.c:5047 get_tree_bdev_flags+0x40e/0x4d0 fs/super.c:1692 vfs_get_tree+0x8f/0x2b0 fs/super.c:1815 do_new_mount+0x2a2/0x9e0 fs/namespace.c:3808 do_mount fs/namespace.c:4136 [inline] __do_sys_mount fs/namespace.c:4347 [inline] __se_sys_mount+0x317/0x410 fs/namespace.c:4324 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline] do_syscall_64+0xfa/0x3b0 arch/x86/entry/syscall_64.c:94 entry_SYSCALL_64_after_hwframe+0x77/0x7f During f2fs_evict_inode(), clear_inode() detects that we missed to truncate all page cache before destorying inode, that is because in below path, we will create page #0 in cache, but missed to drop it in error path, let's fix it. - evict - f2fs_evict_inode - f2fs_truncate - f2fs_convert_inline_inode - f2fs_grab_cache_folio : create page #0 in cache - f2fs_convert_inline_folio : sanity check failed, return -EFSCORRUPTED - clear_inode detects that inode->i_data.nrpages is not zero
Quoted source text, attributed separately from HOL analysis.