CVE-2025-37739: f2fs: fix to avoid out-of-bounds access in f2fs_truncate_inode_blocks()
Noroxi assessment
Priority: Monitor (action score 28/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.20% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 67e16ccba74dd8de0a7b10062f1e02d77432f573, 6ba8b41d0aa4b82f90f0c416cb53fcef9696525d, 8b5e5aac44fee122947a269f9034c048e4c295de; azl3 kernel 6.6.85.1-4 on Azure Linux 3.0 6.6.92.2-1; azl3 kernel 6.6.92.2-1 on Azure Linux 3.0 6.6.92.2-1.
Low priority for now. Upgrade to Linux Linux 67e16ccba74dd8de0a7b10062f1e02d77432f573, 6ba8b41d0aa4b82f90f0c416cb53fcef9696525d, 8b5e5aac44fee122947a269f9034c048e4c295de; azl3 kernel 6.6.85.1-4 on Azure Linux 3.0 6.6.92.2-1; azl3 kernel 6.6.92.2-1 on Azure Linux 3.0 6.6.92.2-1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- May 1, 2025
- Updated
- Jun 17, 2026
- EPSS
- 0.2% · 9th percentile
- CWE
- CWE-125
Report tools
Action score
28
Monitor
Low priority for now.
- CVSS
- 28 / 40 · 7.1 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
| debian | debian linux | cpe:2.3:o:debian:debian_linux |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- debian debian linux11.0
- linux linux kernel5.11 and later · before 5.15.181
- linux linux kernel5.16 and later · before 6.1.135
- linux linux kernel6.2 and later · before 6.6.88
- linux linux kernel3.8 and later · before 5.10.237
- linux linux kernel6.13 and later · before 6.13.12
- linux linux kernel6.14 and later · before 6.14.3
- linux linux kernel6.7 and later · before 6.12.24
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 3.8affected
- 98e4da8ca301e062d79ae168c67e56f3c3de3ce4 and later · before a67e1bf03c609a751d1740a1789af25e599966faaffected · git
- 98e4da8ca301e062d79ae168c67e56f3c3de3ce4 and later · before 67e16ccba74dd8de0a7b10062f1e02d77432f573affected · git
- 98e4da8ca301e062d79ae168c67e56f3c3de3ce4 and later · before 98dbf2af63de0b551082c9bc48333910e009b09faffected · git
- 98e4da8ca301e062d79ae168c67e56f3c3de3ce4 and later · before 8b5e5aac44fee122947a269f9034c048e4c295deaffected · git
- 98e4da8ca301e062d79ae168c67e56f3c3de3ce4 and later · before ecc461331604b07cdbdb7360dbdf78471653264caffected · git
- 98e4da8ca301e062d79ae168c67e56f3c3de3ce4 and later · before d7242fd7946d4cba0411effb6b5048ca55125747affected · git
- 98e4da8ca301e062d79ae168c67e56f3c3de3ce4 and later · before 6ba8b41d0aa4b82f90f0c416cb53fcef9696525daffected · git
- 98e4da8ca301e062d79ae168c67e56f3c3de3ce4 and later · before e6494977bd4a83862118a05f57a8df40256951c0affected · git
- before 3.8not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.135-1 | 6.1.135-1 |
| Debian:13 | linux | before 6.12.25-1 | 6.12.25-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2025-23162May 1, 2025 · drm/xe/vf: Don't try to trigger a full GT reset if VF22Monitor
- ← EarlierCVE-2025-23163May 1, 2025 · net: vlan: don't propagate flags on open22Monitor
- Later →CVE-2025-37740May 1, 2025 · jfs: add sanity check for agwidth in dbMount22Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 67e16ccba74dd8de0a7b10062f1e02d77432f573 | Vendor (CNA) |
| Linux Linux | 6ba8b41d0aa4b82f90f0c416cb53fcef9696525d | Vendor (CNA) |
| Linux Linux | 8b5e5aac44fee122947a269f9034c048e4c295de | Vendor (CNA) |
| Linux Linux | 98dbf2af63de0b551082c9bc48333910e009b09f | Vendor (CNA) |
| Linux Linux | a67e1bf03c609a751d1740a1789af25e599966fa | Vendor (CNA) |
| Linux Linux | d7242fd7946d4cba0411effb6b5048ca55125747 | Vendor (CNA) |
| Linux Linux | e6494977bd4a83862118a05f57a8df40256951c0 | Vendor (CNA) |
| Linux Linux | ecc461331604b07cdbdb7360dbdf78471653264c | Vendor (CNA) |
| azl3 kernel 6.6.85.1-4 on Azure Linux 3.0 | 6.6.92.2-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| azl3 kernel 6.6.92.2-1 on Azure Linux 3.0 | 6.6.92.2-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| debian:linux | 6.1.135-1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-125 · Out-of-bounds ReadCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (9 more)Show less
- git.kernel.org/stable/c/6ba8b41d0aa4b82f90f0c416cb53fcef9696525d
- git.kernel.org/stable/c/8b5e5aac44fee122947a269f9034c048e4c295de
- git.kernel.org/stable/c/98dbf2af63de0b551082c9bc48333910e009b09f
- git.kernel.org/stable/c/a67e1bf03c609a751d1740a1789af25e599966fa
- git.kernel.org/stable/c/d7242fd7946d4cba0411effb6b5048ca55125747
- git.kernel.org/stable/c/e6494977bd4a83862118a05f57a8df40256951c0
- git.kernel.org/stable/c/ecc461331604b07cdbdb7360dbdf78471653264c
- lists.debian.org/debian-lts-announce/2025/05/msg00030.html
- lists.debian.org/debian-lts-announce/2025/05/msg00045.html
Vendor advisories and official records. Exploit/PoC links are deliberately left out.