cbcvebase.
CVE-2024-50229
published 2024-11-09

CVE-2024-50229: In the Linux kernel, the following vulnerability has been resolved: nilfs2: fix potential deadlock with newly created symlinks Syzbot reported that…

PriorityP419medium5.5CVSS 3.1
AVLACLPRLUINSUCNINAH
EPSS
0.21%
10.8th percentile
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.

Affected

37 ranges· showing 25
VendorProductVersion rangeFixed in
debianlinux< linux 6.1.119-1 (bookworm)linux 6.1.119-1 (bookworm)
debianlinux-6.1< linux 6.1.119-1 (bookworm)linux 6.1.119-1 (bookworm)
linuxlinux
linuxlinux
linuxlinux>= 21fc61c73c3903c4c312d0802da01ec2b323d174 < cc38c596e648575ce58bfc31623a6506eda4b94acc38c596e648575ce58bfc31623a6506eda4b94a
linuxlinux>= 21fc61c73c3903c4c312d0802da01ec2b323d174 < a1686db1e59f8fc016c4c9361e2119dd206f479aa1686db1e59f8fc016c4c9361e2119dd206f479a
linuxlinux>= 21fc61c73c3903c4c312d0802da01ec2b323d174 < c72e0df0b56c1166736dc8eb62070ebb12591447c72e0df0b56c1166736dc8eb62070ebb12591447
linuxlinux>= 21fc61c73c3903c4c312d0802da01ec2b323d174 < 69548bb663fcb63f9ee0301be808a36b9d78dac369548bb663fcb63f9ee0301be808a36b9d78dac3
linuxlinux>= 21fc61c73c3903c4c312d0802da01ec2b323d174 < 58c7f44c7b9e5ac7e3b1e5da2572ed7767a12f3858c7f44c7b9e5ac7e3b1e5da2572ed7767a12f38
linuxlinux>= 21fc61c73c3903c4c312d0802da01ec2b323d174 < 1246d86e7bbde265761932c6e2dce28c69cdcb911246d86e7bbde265761932c6e2dce28c69cdcb91
linuxlinux>= 21fc61c73c3903c4c312d0802da01ec2b323d174 < 9aa5d43ac4cace8fb9bd964ff6c23f599dc3cd249aa5d43ac4cace8fb9bd964ff6c23f599dc3cd24
linuxlinux>= 21fc61c73c3903c4c312d0802da01ec2b323d174 < b3a033e3ecd3471248d474ef263aadc0059e516ab3a033e3ecd3471248d474ef263aadc0059e516a
linuxlinux>= 4.4.116 < 4.54.5
linuxlinux_kernel
linuxlinux_kernel
linuxlinux_kernel>= 0 < 5.10.234-15.10.234-1
linuxlinux_kernel>= 0 < 6.1.119-16.1.119-1
linuxlinux_kernel>= 0 < 6.11.7-16.11.7-1
linuxlinux_kernel>= 0 < 6.11.7-16.11.7-1
linuxlinux_kernel>= 0 < 5.4.0-208.2285.4.0-208.228
linuxlinux_kernel>= 0 < 5.15.0-133.1445.15.0-133.144
linuxlinux_kernel>= 0 < 6.8.0-56.586.8.0-56.58
linuxlinux_kernel>= 0 < 6.11.0-18.186.11.0-18.18
linuxlinux_kernel>= 0 < 4.15.0-235.2474.15.0-235.247
linuxlinux_kernel>= 4.20 < 5.4.2855.4.285

CVSS provenance

nvdv3.15.5MEDIUMCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
osv8.8HIGH
vendor_ubuntu8.8HIGH
vendor_debian5.5MEDIUM
vendor_msrc5.5MEDIUM
vendor_redhat5.5MEDIUM
Stop checking back — get the weekly exploitation signal.

Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.