System hang via reversed F2FS lock order
Published Dec 29, 2024 · Updated May 23, 2026
Improper locking in the Linux kernel F2FS implementation allows local users to hang the system through filesystem activity. The f2fs_record_stop_reason() path takes sbi->sb_lock while inode eviction holds sb_internal, but committing the superblock can enter filesystem reclaim and recreate the opposite lock order. Exploitation requires local low-privileged access and a mounted F2FS filesystem; the resulting circular dependency can deadlock kernel work and interrupt service.
Summary
What happened
Improper locking in the Linux kernel F2FS implementation allows local users to hang the system through filesystem activity. The f2fs_record_stop_reason() path takes sbi->sb_lock while inode eviction holds sb_internal, but committing the superblock can enter filesystem reclaim and recreate the opposite lock order. Exploitation requires local low-privileged access and a mounted F2FS filesystem; the resulting circular dependency can deadlock kernel work and interrupt service.
The record
- CVE
- CVE-2024-56744
- Published
- Dec 29, 2024
- Updated
- May 23, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-667, T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Dec 29, 2024CVE publishedPublication date reported by the CVE source.
- May 23, 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=6.4.4 <6.5
- Affected versionversion=6.5
- Affected versionversion=b62e71be2110d8b52bf5faf3c3ed7ca1a0c113a5 <1539a088b108996bcdaddb7775070b5163b14233
- Affected versionversion=b62e71be2110d8b52bf5faf3c3ed7ca1a0c113a5 <801092a2c9c251ef6a8678fcb8fcc1220474a697
- Affected versionversion=b62e71be2110d8b52bf5faf3c3ed7ca1a0c113a5 <ecf4e6782b01fd578b565b3dd2be7bb0ac91082e
- Affected versionversion=b62e71be2110d8b52bf5faf3c3ed7ca1a0c113a5 <f10a890308a7cd8794e21f646f09827c6cb4bf5d
- Affected versionversion=ed1d478bf838820201f3fb67a1748fdf15954ea4
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