Kernel memory disclosure and crash via inode truncation
Published May 1, 2025 · Updated May 11, 2026
Out-of-bounds read in the Linux F2FS implementation allows local users to disclose kernel memory or crash the system. During zero-length inode truncation, f2fs_do_truncate_blocks can leave free_from at zero when a reused NAT address yields a non-inode node page; f2fs_truncate_inode_blocks then passes zero offsets to get_nid, which indexes i_nid at -924. Exploitation requires low-privileged local access and an affected F2FS state involving reused node-block addresses.
Summary
What happened
Out-of-bounds read in the Linux F2FS implementation allows local users to disclose kernel memory or crash the system. During zero-length inode truncation, f2fs_do_truncate_blocks can leave free_from at zero when a reused NAT address yields a non-inode node page; f2fs_truncate_inode_blocks then passes zero offsets to get_nid, which indexes i_nid at -924. Exploitation requires low-privileged local access and an affected F2FS state involving reused node-block addresses.
The record
- CVE
- CVE-2025-37739
- Published
- May 1, 2025
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-125
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- May 1, 2025CVE publishedPublication date reported by the CVE source.
- May 11, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=3.8
- Affected versionversion=98e4da8ca301e062d79ae168c67e56f3c3de3ce4 <67e16ccba74dd8de0a7b10062f1e02d77432f573
- Affected versionversion=98e4da8ca301e062d79ae168c67e56f3c3de3ce4 <6ba8b41d0aa4b82f90f0c416cb53fcef9696525d
- Affected versionversion=98e4da8ca301e062d79ae168c67e56f3c3de3ce4 <8b5e5aac44fee122947a269f9034c048e4c295de
- Affected versionversion=98e4da8ca301e062d79ae168c67e56f3c3de3ce4 <98dbf2af63de0b551082c9bc48333910e009b09f
- Affected versionversion=98e4da8ca301e062d79ae168c67e56f3c3de3ce4 <a67e1bf03c609a751d1740a1789af25e599966fa
- Affected versionversion=98e4da8ca301e062d79ae168c67e56f3c3de3ce4 <d7242fd7946d4cba0411effb6b5048ca55125747
- Affected versionversion=98e4da8ca301e062d79ae168c67e56f3c3de3ce4 <e6494977bd4a83862118a05f57a8df40256951c0
- Affected versionversion=98e4da8ca301e062d79ae168c67e56f3c3de3ce4 <ecc461331604b07cdbdb7360dbdf78471653264c
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo