CVE-2025-40137: f2fs: fix to truncate first page in error path of f2fs_truncate()
Noroxi assessment
Priority: Monitor (action score 0/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.21% (FIRST EPSS).
- Fixed version: Linux Linux 3500d7e1ba53f39bdb8a5aa9c2066b2f08e8c92e, 3b0c8908faa18cded84d64822882a830ab1f4d26, 83a8e4efea022506a0e049e7206bdf8be9f78148.
Low priority for now. Upgrade to Linux Linux 3500d7e1ba53f39bdb8a5aa9c2066b2f08e8c92e, 3b0c8908faa18cded84d64822882a830ab1f4d26, 83a8e4efea022506a0e049e7206bdf8be9f78148 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 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
- Published
- Nov 12, 2025
- Updated
- Oct 30, 2026
- EPSS
- 0.2% · 11th percentile
- CWE
- —
Report tools
Action score
0
Monitor
Low priority for now.
- CVSS
- 0 / 40 · —
- 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.
—
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.19affected
- 92dffd01790a5219d234fc83c3ba854f4490b7f4 and later · before 3500d7e1ba53f39bdb8a5aa9c2066b2f08e8c92eaffected · git
- 92dffd01790a5219d234fc83c3ba854f4490b7f4 and later · before 83a8e4efea022506a0e049e7206bdf8be9f78148affected · git
- 92dffd01790a5219d234fc83c3ba854f4490b7f4 and later · before a7b7ebdd7045a36454b3e388a2ecf50344fad9e6affected · git
- 92dffd01790a5219d234fc83c3ba854f4490b7f4 and later · before 3b0c8908faa18cded84d64822882a830ab1f4d26affected · git
- 92dffd01790a5219d234fc83c3ba854f4490b7f4 and later · before 9251a9e6e871cb03c4714a18efa8f5d4a8818450affected · git
- before 3.19not affected · semver
- 6.1.191 and later · up to and including 6.1.*not affected · semver
- 6.6.112 and later · up to and including 6.6.*not affected · semver
- 6.12.53 and later · up to and including 6.12.*not 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 | from 0 | — |
| Debian:13 | linux | before 6.12.57-1 | 6.12.57-1 |
| Debian:14 | linux | before 6.17.6-1 | 6.17.6-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2025-40135Nov 12, 2025 · ipv6: use RCU in ip6_xmit()32Monitor
- ← EarlierCVE-2025-40136Nov 12, 2025 · crypto: hisilicon/qm - request reserved interrupt for virtual function0Monitor
- Later →CVE-2025-40138Nov 12, 2025 · f2fs: fix to avoid NULL pointer dereference in f2fs_check_quota_consistency()0Monitor
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 | 3500d7e1ba53f39bdb8a5aa9c2066b2f08e8c92e | Vendor (CNA) |
| Linux Linux | 3b0c8908faa18cded84d64822882a830ab1f4d26 | Vendor (CNA) |
| Linux Linux | 83a8e4efea022506a0e049e7206bdf8be9f78148 | Vendor (CNA) |
| Linux Linux | 9251a9e6e871cb03c4714a18efa8f5d4a8818450 | Vendor (CNA) |
| Linux Linux | a7b7ebdd7045a36454b3e388a2ecf50344fad9e6 | Vendor (CNA) |
| debian:linux | 6.12.57-1 · Debian:13 | 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
No CVSS vector for this record, so attack conditions can't be derived.
Weakness class (CWE)
—
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (4 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.