Kernel crash via malformed F2FS dnode image
Published Aug 30, 2025 · Updated Aug 5, 2026
Out-of-bounds access in the F2FS driver in Linux allows local users to crash the kernel by triggering a write on a corrupted filesystem image. The f2fs_get_dnode_of_data function parses a dnode whose node identifier matches its inode as an inode node, then computes a block-address offset beyond the page boundary. Exploitation requires local access and kernel processing of crafted F2FS metadata during a write; the established consequence is a kernel crash without integrity impact.
Summary
What happened
Out-of-bounds access in the F2FS driver in Linux allows local users to crash the kernel by triggering a write on a corrupted filesystem image. The f2fs_get_dnode_of_data function parses a dnode whose node identifier matches its inode as an inode node, then computes a block-address offset beyond the page boundary. Exploitation requires local access and kernel processing of crafted F2FS metadata during a write; the established consequence is a kernel crash without integrity impact.
The record
- CVE
- CVE-2025-38677
- Published
- Aug 30, 2025
- Updated
- Aug 5, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-20, T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 30, 2025CVE publishedPublication date reported by the CVE source.
- Aug 5, 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 <6b7784ea07e6aa044f74b39d6b5af5e28746fc81
- Affected versionversion=98e4da8ca301e062d79ae168c67e56f3c3de3ce4 <77de19b6867f2740cdcb6c9c7e50d522b47847a4
- Affected versionversion=98e4da8ca301e062d79ae168c67e56f3c3de3ce4 <888aa660144bcb6ec07839da756ee46bfcf7fc53
- Affected versionversion=98e4da8ca301e062d79ae168c67e56f3c3de3ce4 <901f62efd6e855f93d8b1175540f29f4dc45ba55
- Affected versionversion=98e4da8ca301e062d79ae168c67e56f3c3de3ce4 <92ef491b506a0f4dd971a3a76f86f2d8f5370180
- Affected versionversion=98e4da8ca301e062d79ae168c67e56f3c3de3ce4 <a650654365c57407413e9b1f6ff4d539bf2e99ca
- Affected versionversion=98e4da8ca301e062d79ae168c67e56f3c3de3ce4 <ee4d13f5407cbdf1216cc258f45492075713889a
- Affected versionversion=98e4da8ca301e062d79ae168c67e56f3c3de3ce4 <f1d5093d9fe9f3c74c123741c88666cc853b79c5
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