CVE-2024-50229: Linux kernel · nilfs2: fix potential deadlock with newly created symlinks
Source GCVE Database
Not known to be exploited · CVSS 5.5 Medium.
Data as of 29 Oct 2026, 23:14 UTC
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 9 Nov 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.
What to do
AI-suggested
A fix for this issue has been implemented in the Linux kernel by dropping the __GFP_FS flag from the GFP flags of newly created symlinks in nilfs2. Users should apply the official kernel updates that include this fix once available. Until then, no specific workaround is detailed. Monitoring vendor advisories for patch releases is recommended.
Description
CVE-2024-50229 is a medium-severity vulnerability in the Linux kernel's nilfs2 filesystem. It involves a potential deadlock triggered by newly created symbolic links due to improper GFP flag handling during memory allocation. This flaw can cause circular lock dependencies leading to deadlocks when certain semaphores are held during filesystem operations. The issue arises from a change that overwrites GFP flags to GFP_KERNEL without dropping the __GFP_FS flag for new symlinks, unlike symlinks read from backing devices. The fix involves dropping the __GFP_FS flag for newly created symlinks to prevent the deadlock condition.
References
- nvd.nist.gov/vuln/detail/CVE-2024-50229 (opens in a new tab)
- git.kernel.org/stable/c/1246d86e7bbde265761932c6e2dce28c69cdcb91 (opens in a new tab)
- git.kernel.org/stable/c/58c7f44c7b9e5ac7e3b1e5da2572ed7767a12f38 (opens in a new tab)
- git.kernel.org/stable/c/69548bb663fcb63f9ee0301be808a36b9d78dac3 (opens in a new tab)
- git.kernel.org/stable/c/9aa5d43ac4cace8fb9bd964ff6c23f599dc3cd24 (opens in a new tab)
- git.kernel.org/stable/c/a1686db1e59f8fc016c4c9361e2119dd206f479a (opens in a new tab)
- git.kernel.org/stable/c/b3a033e3ecd3471248d474ef263aadc0059e516a (opens in a new tab)
- git.kernel.org/stable/c/c72e0df0b56c1166736dc8eb62070ebb12591447 (opens in a new tab)
- git.kernel.org/stable/c/cc38c596e648575ce58bfc31623a6506eda4b94a (opens in a new tab)
- lists.debian.org/debian-lts-announce/2025/01/msg00001.html (opens in a new tab)
- lists.debian.org/debian-lts-announce/2025/03/msg00002.html (opens in a new tab)