System hang via duplicate f2fs inode locking
Published Jul 10, 2025 · Updated May 12, 2026
Improper input validation in the f2fs code used by Linux and SIMATIC CN 4100 before V5.0 allows local users to hang the system. The inode path accepts metadata whose xattr_nid equals the directory inode number, so mknod locks the same inode page twice and deadlocks. Exploitation requires local low-privileged access and a mounted corrupted f2fs image; the demonstrated consequence is a persistent task hang.
Summary
What happened
Improper input validation in the f2fs code used by Linux and SIMATIC CN 4100 before V5.0 allows local users to hang the system. The inode path accepts metadata whose xattr_nid equals the directory inode number, so mknod locks the same inode page twice and deadlocks. Exploitation requires local low-privileged access and a mounted corrupted f2fs image; the demonstrated consequence is a persistent task hang.
The record
- CVE
- CVE-2025-38347
- Published
- Jul 10, 2025
- Updated
- May 12, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-20, T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 10, 2025CVE publishedPublication date reported by the CVE source.
- May 12, 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 <061cf3a84bde038708eb0f1d065b31b7c2456533
- Affected versionversion=98e4da8ca301e062d79ae168c67e56f3c3de3ce4 <44e904a1ad09e84039058dcbbb1b9ea5b8d7d75d
- Affected versionversion=98e4da8ca301e062d79ae168c67e56f3c3de3ce4 <5a06d97d5340c00510f24e80e8de821bd3bd9285
- Affected versionversion=98e4da8ca301e062d79ae168c67e56f3c3de3ce4 <aaddc6c696bd1bff20eaacfa88579d6eae64d541
- Affected versionversion=98e4da8ca301e062d79ae168c67e56f3c3de3ce4 <c4029044cc408b149e63db7dc8617a0783a3f10d
- Affected versionversion=98e4da8ca301e062d79ae168c67e56f3c3de3ce4 <e98dc1909f3d5bc078ec7a605524f1e3f4c0eb14
- Affected versionversion=98e4da8ca301e062d79ae168c67e56f3c3de3ce4 <ecff54aa20b5b21db82e63e46066b55e43d72e78
- Affected versionversion=98e4da8ca301e062d79ae168c67e56f3c3de3ce4 <fed611bd8c7b76b070aa407d0c7558e20d9e1f68
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.
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