CVE - CVE-2024-50229

CVE-ID
CVE-2024-50229	Learn more at National Vulnerability Database (NVD) • CVSS Severity Rating • Fix Information • Vulnerable Software Versions • SCAP Mappings • CPE Information
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.
References
Note: References are provided for the convenience of the reader to help distinguish between vulnerabilities. The list is not intended to be complete.
MISC:https://git.kernel.org/stable/c/1246d86e7bbde265761932c6e2dce28c69cdcb91 URL:https://git.kernel.org/stable/c/1246d86e7bbde265761932c6e2dce28c69cdcb91 MISC:https://git.kernel.org/stable/c/58c7f44c7b9e5ac7e3b1e5da2572ed7767a12f38 URL:https://git.kernel.org/stable/c/58c7f44c7b9e5ac7e3b1e5da2572ed7767a12f38 MISC:https://git.kernel.org/stable/c/69548bb663fcb63f9ee0301be808a36b9d78dac3 URL:https://git.kernel.org/stable/c/69548bb663fcb63f9ee0301be808a36b9d78dac3 MISC:https://git.kernel.org/stable/c/9aa5d43ac4cace8fb9bd964ff6c23f599dc3cd24 URL:https://git.kernel.org/stable/c/9aa5d43ac4cace8fb9bd964ff6c23f599dc3cd24 MISC:https://git.kernel.org/stable/c/a1686db1e59f8fc016c4c9361e2119dd206f479a URL:https://git.kernel.org/stable/c/a1686db1e59f8fc016c4c9361e2119dd206f479a MISC:https://git.kernel.org/stable/c/b3a033e3ecd3471248d474ef263aadc0059e516a URL:https://git.kernel.org/stable/c/b3a033e3ecd3471248d474ef263aadc0059e516a MISC:https://git.kernel.org/stable/c/c72e0df0b56c1166736dc8eb62070ebb12591447 URL:https://git.kernel.org/stable/c/c72e0df0b56c1166736dc8eb62070ebb12591447 MISC:https://git.kernel.org/stable/c/cc38c596e648575ce58bfc31623a6506eda4b94a URL:https://git.kernel.org/stable/c/cc38c596e648575ce58bfc31623a6506eda4b94a
Assigning CNA
kernel.org
Date Record Created
20241021	Disclaimer: The record creation date may reflect when the CVE ID was allocated or reserved, and does not necessarily indicate when this vulnerability was discovered, shared with the affected vendor, publicly disclosed, or updated in CVE.
Phase (Legacy)
Assigned (20241021)
Votes (Legacy)

Comments (Legacy)

Proposed (Legacy)
N/A
This is an record on the CVE List, which provides common identifiers for publicly known cybersecurity vulnerabilities.
Search CVE Using Keywords: You can also search by reference using the CVE Reference Maps.
For More Information: CVE Request Web Form (select "Other" from dropdown)