Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2024-50229nilfs2: fix potential deadlock with newly created symlinks

Description

In the Linux kernel, the following vulnerability has been resolved: nilfs2: fix potential deadlock with newly created symlinks Syzbot reported that page_symlink(), called by nilfs_symlink(), triggers memory reclamation involving the filesystem layer, which can result in circular lock dependencies among the reader/writer semaphore nilfs->ns_segctor_sem, s_writers percpu_rwsem (intwrite) and the fs_reclaim pseudo lock. This is because after commit 21fc61c73c39 ("don't put symlink bodies in pagecache into highmem"), the gfp flags of the page cache for symbolic links are overwritten to GFP_KERNEL via inode_nohighmem(). This is not a problem for symlinks read from the backing device, because the __GFP_FS flag is dropped after inode_nohighmem() is called. However, when a new symlink is created with nilfs_symlink(), the gfp flags remain overwritten to GFP_KERNEL. Then, memory allocation called from page_symlink() etc. triggers memory reclamation including the FS layer, which may call nilfs_evict_inode() or nilfs_dirty_inode(). And these can cause a deadlock if they are called while nilfs->ns_segctor_sem is held: Fix this issue by dropping the __GFP_FS flag from the page cache GFP flags of newly created symlinks in the same way that nilfs_new_inode() and __nilfs_read_inode() do, as a workaround until we adopt nofs allocation scope consistently or improve the locking constraints.

Timeline

  1. ID reserved

    By Linux

  2. · 19 days later

    Published

  3. · 19 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2024-50229, by who scored it
Scored byCVSSScoreVector
CISA-ADPADP (enrichment)3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
NVDNVD · Modified3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.21% · top 89% of all CVEs (15 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.

Affected products

  • Linux · Linux

    • affected 21fc61c73c3903c4c312d0802da01ec2b323d174 – < cc38c596e648575ce58bfc31623a6506eda4b94a
    • affected 21fc61c73c3903c4c312d0802da01ec2b323d174 – < a1686db1e59f8fc016c4c9361e2119dd206f479a
    • affected 21fc61c73c3903c4c312d0802da01ec2b323d174 – < c72e0df0b56c1166736dc8eb62070ebb12591447
    • affected 21fc61c73c3903c4c312d0802da01ec2b323d174 – < 69548bb663fcb63f9ee0301be808a36b9d78dac3
    • affected 21fc61c73c3903c4c312d0802da01ec2b323d174 – < 58c7f44c7b9e5ac7e3b1e5da2572ed7767a12f38
    • affected 21fc61c73c3903c4c312d0802da01ec2b323d174 – < 1246d86e7bbde265761932c6e2dce28c69cdcb91
    • affected 21fc61c73c3903c4c312d0802da01ec2b323d174 – < 9aa5d43ac4cace8fb9bd964ff6c23f599dc3cd24
    • affected 21fc61c73c3903c4c312d0802da01ec2b323d174 – < b3a033e3ecd3471248d474ef263aadc0059e516a
    • affected 076e4ab3279eb3ddb206de44d04df7aeb2428e09
    • affected 4.4.116 – < 4.5
  • Linux · Linux

    • affected 4.5
    • unaffected < 4.5
    • unaffected 4.19.323 – ≤ 4.19.*
    • unaffected 5.4.285 – ≤ 5.4.*
    • unaffected 5.10.229 – ≤ 5.10.*
    • unaffected 5.15.171 – ≤ 5.15.*
    • unaffected 6.1.116 – ≤ 6.1.*
    • unaffected 6.6.60 – ≤ 6.6.*
    • unaffected 6.11.7 – ≤ 6.11.*
    • unaffected 6.12 – ≤ *

References

References10

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2024-50229 badge
[![CVE-2024-50229](https://cveledger.app/badge/CVE-2024-50229.svg)](https://cveledger.app/cve/CVE-2024-50229)

Record last updated .