CVE-2025-37739f2fs: fix to avoid out-of-bounds access in f2fs_truncate_inode_blocks()
- 7.1HighCVSS base score
- 0.20%Exploitation in 30 daysEPSS · top 90% 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 avoid out-of-bounds access in f2fs_truncate_inode_blocks() syzbot reports an UBSAN issue as below: ------------[ cut here ]------------ UBSAN: array-index-out-of-bounds in fs/f2fs/node.h:381:10 index 18446744073709550692 is out of range for type '__le32[5]' (aka 'unsigned int[5]') CPU: 0 UID: 0 PID: 5318 Comm: syz.0.0 Not tainted 6.14.0-rc3-syzkaller-00060-g6537cfb395f3 #0 Call Trace: <TASK> __dump_stack lib/dump_stack.c:94 [inline] dump_stack_lvl+0x241/0x360 lib/dump_stack.c:120 ubsan_epilogue lib/ubsan.c:231 [inline] __ubsan_handle_out_of_bounds+0x121/0x150 lib/ubsan.c:429 get_nid fs/f2fs/node.h:381 [inline] f2fs_truncate_inode_blocks+0xa5e/0xf60 fs/f2fs/node.c:1181 f2fs_do_truncate_blocks+0x782/0x1030 fs/f2fs/file.c:808 f2fs_truncate_blocks+0x10d/0x300 fs/f2fs/file.c:836 f2fs_truncate+0x417/0x720 fs/f2fs/file.c:886 f2fs_file_write_iter+0x1bdb/0x2550 fs/f2fs/file.c:5093 aio_write+0x56b/0x7c0 fs/aio.c:1633 io_submit_one+0x8a7/0x18a0 fs/aio.c:2052 __do_sys_io_submit fs/aio.c:2111 [inline] __se_sys_io_submit+0x171/0x2e0 fs/aio.c:2081 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0xf3/0x230 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x77/0x7f RIP: 0033:0x7f238798cde9 index 18446744073709550692 (decimal, unsigned long long) = 0xfffffffffffffc64 (hexadecimal, unsigned long long) = -924 (decimal, long long) In f2fs_truncate_inode_blocks(), UBSAN detects that get_nid() tries to access .i_nid[-924], it means both offset[0] and level should zero. The possible case should be in f2fs_do_truncate_blocks(), we try to truncate inode size to zero, however, dn.ofs_in_node is zero and dn.node_page is not an inode page, so it fails to truncate inode page, and then pass zeroed free_from to f2fs_truncate_inode_blocks(), result in this issue. if (dn.ofs_in_node || IS_INODE(dn.node_page)) { f2fs_truncate_data_blocks_range(&dn, count); free_from += count; } I guess the reason why dn.node_page is not an inode page could be: there are multiple nat entries share the same node block address, once the node block address was reused, f2fs_get_node_page() may load a non-inode block. Let's add a sanity check for such condition to avoid out-of-bounds access issue.
Timeline
ID reserved
By Linux
- 15 days later
· 15 days later
Published
- 13 months later
· 13 months 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
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| NVDNVD · Analyzed | 3.1 | High7.1 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H |
- EPSS (exploitation in 30 days)
- 0.20% · top 90% of all CVEs (15 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.1.
Affected products
- affected 98e4da8ca301e062d79ae168c67e56f3c3de3ce4 – < a67e1bf03c609a751d1740a1789af25e599966fa
- affected 98e4da8ca301e062d79ae168c67e56f3c3de3ce4 – < 67e16ccba74dd8de0a7b10062f1e02d77432f573
- affected 98e4da8ca301e062d79ae168c67e56f3c3de3ce4 – < 98dbf2af63de0b551082c9bc48333910e009b09f
- affected 98e4da8ca301e062d79ae168c67e56f3c3de3ce4 – < 8b5e5aac44fee122947a269f9034c048e4c295de
- affected 98e4da8ca301e062d79ae168c67e56f3c3de3ce4 – < ecc461331604b07cdbdb7360dbdf78471653264c
- affected 98e4da8ca301e062d79ae168c67e56f3c3de3ce4 – < d7242fd7946d4cba0411effb6b5048ca55125747
- affected 98e4da8ca301e062d79ae168c67e56f3c3de3ce4 – < 6ba8b41d0aa4b82f90f0c416cb53fcef9696525d
- affected 98e4da8ca301e062d79ae168c67e56f3c3de3ce4 – < e6494977bd4a83862118a05f57a8df40256951c0
- affected 3.8
- unaffected < 3.8
- unaffected 5.10.237 – ≤ 5.10.*
- unaffected 5.15.181 – ≤ 5.15.*
- unaffected 6.1.135 – ≤ 6.1.*
- unaffected 6.6.88 – ≤ 6.6.*
- unaffected 6.12.24 – ≤ 6.12.*
- unaffected 6.13.12 – ≤ 6.13.*
- unaffected 6.14.3 – ≤ 6.14.*
- unaffected 6.15 – ≤ *
References
References10
- https://git.kernel.org/stable/c/a67e1bf03c609a751d1740a1789af25e599966fa (opens in a new tab)
- https://git.kernel.org/stable/c/67e16ccba74dd8de0a7b10062f1e02d77432f573 (opens in a new tab)
- https://git.kernel.org/stable/c/98dbf2af63de0b551082c9bc48333910e009b09f (opens in a new tab)
- https://git.kernel.org/stable/c/8b5e5aac44fee122947a269f9034c048e4c295de (opens in a new tab)
- https://git.kernel.org/stable/c/ecc461331604b07cdbdb7360dbdf78471653264c (opens in a new tab)
- https://git.kernel.org/stable/c/d7242fd7946d4cba0411effb6b5048ca55125747 (opens in a new tab)
- https://git.kernel.org/stable/c/6ba8b41d0aa4b82f90f0c416cb53fcef9696525d (opens in a new tab)
- https://git.kernel.org/stable/c/e6494977bd4a83862118a05f57a8df40256951c0 (opens in a new tab)
- https://lists.debian.org/debian-lts-announce/2025/05/msg00045.html (opens in a new tab)
- https://lists.debian.org/debian-lts-announce/2025/05/msg00030.html (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-2025-13073 (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-2025-37739)Record last updated .