Kernel hang via nilfs2 symlink reclaim deadlock
Published Nov 9, 2024 · Updated May 23, 2026
Deadlock in Linux nilfs2 allows local users to hang affected kernels by creating a symlink while filesystem memory reclamation is possible. The nilfs_symlink path leaves __GFP_FS enabled in the new symlink page cache, so page_symlink can enter filesystem reclaim and reacquire locks while ns_segctor_sem is held. Exploitation requires local access to create a symlink on a mounted nilfs2 filesystem and memory pressure sufficient to invoke filesystem reclaim.
Summary
What happened
Deadlock in Linux nilfs2 allows local users to hang affected kernels by creating a symlink while filesystem memory reclamation is possible. The nilfs_symlink path leaves __GFP_FS enabled in the new symlink page cache, so page_symlink can enter filesystem reclaim and reacquire locks while ns_segctor_sem is held. Exploitation requires local access to create a symlink on a mounted nilfs2 filesystem and memory pressure sufficient to invoke filesystem reclaim.
The record
- CVE
- CVE-2024-50229
- Published
- Nov 9, 2024
- Updated
- May 23, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-667, T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Nov 9, 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=076e4ab3279eb3ddb206de44d04df7aeb2428e09
- Affected versionversion=21fc61c73c3903c4c312d0802da01ec2b323d174 <1246d86e7bbde265761932c6e2dce28c69cdcb91
- Affected versionversion=21fc61c73c3903c4c312d0802da01ec2b323d174 <58c7f44c7b9e5ac7e3b1e5da2572ed7767a12f38
- Affected versionversion=21fc61c73c3903c4c312d0802da01ec2b323d174 <69548bb663fcb63f9ee0301be808a36b9d78dac3
- Affected versionversion=21fc61c73c3903c4c312d0802da01ec2b323d174 <9aa5d43ac4cace8fb9bd964ff6c23f599dc3cd24
- Affected versionversion=21fc61c73c3903c4c312d0802da01ec2b323d174 <a1686db1e59f8fc016c4c9361e2119dd206f479a
- Affected versionversion=21fc61c73c3903c4c312d0802da01ec2b323d174 <b3a033e3ecd3471248d474ef263aadc0059e516a
- Affected versionversion=21fc61c73c3903c4c312d0802da01ec2b323d174 <c72e0df0b56c1166736dc8eb62070ebb12591447
- Affected versionversion=21fc61c73c3903c4c312d0802da01ec2b323d174 <cc38c596e648575ce58bfc31623a6506eda4b94a
- Affected versionversion=4.4.116 <4.5
- Affected versionversion=4.5
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