UBUNTU-CVE-2024-50229
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.
02 / AFFECTED SOFTWARE
Affected packages
12 explicit affected versions
14 explicit affected versions
99 explicit affected versions
15 explicit affected versions
1 explicit affected versions
1 explicit affected versions
1 explicit affected versions
12 explicit affected versions
11 explicit affected versions
58 explicit affected versions
14 explicit affected versions
41 explicit affected versions
19 explicit affected versions
101 explicit affected versions
44 explicit affected versions
37 explicit affected versions
23 explicit affected versions
19 explicit affected versions
121 explicit affected versions
62 explicit affected versions
51 explicit affected versions
74 explicit affected versions
8 explicit affected versions
24 explicit affected versions
5 explicit affected versions
8 explicit affected versions
1 explicit affected versions
10 explicit affected versions
7 explicit affected versions
2 explicit affected versions
91 explicit affected versions
33 explicit affected versions
63 explicit affected versions
1 explicit affected versions
21 explicit affected versions
16 explicit affected versions
10 explicit affected versions
12 explicit affected versions
10 explicit affected versions
41 explicit affected versions
57 explicit affected versions
50 explicit affected versions
6 explicit affected versions
10 explicit affected versions
12 explicit affected versions
19 explicit affected versions
6 explicit affected versions
67 explicit affected versions
19 explicit affected versions
52 explicit affected versions
72 explicit affected versions
60 explicit affected versions
53 explicit affected versions
11 explicit affected versions
17 explicit affected versions
59 explicit affected versions
7 explicit affected versions
99 explicit affected versions
13 explicit affected versions
69 explicit affected versions
16 explicit affected versions
35 explicit affected versions
19 explicit affected versions
19 explicit affected versions
18 explicit affected versions
18 explicit affected versions
100 explicit affected versions
13 explicit affected versions
4 explicit affected versions
23 explicit affected versions
24 explicit affected versions
1 explicit affected versions
56 explicit affected versions
20 explicit affected versions
7 explicit affected versions
12 explicit affected versions
1 explicit affected versions
50 explicit affected versions
12 explicit affected versions
14 explicit affected versions
7 explicit affected versions
1 explicit affected versions
88 explicit affected versions
12 explicit affected versions
104 explicit affected versions
112 explicit affected versions
34 explicit affected versions
1 explicit affected versions
11 explicit affected versions
6 explicit affected versions
10 explicit affected versions
37 explicit affected versions
13 explicit affected versions
37 explicit affected versions
26 explicit affected versions
13 explicit affected versions
12 explicit affected versions
14 explicit affected versions
29 explicit affected versions
92 explicit affected versions
13 explicit affected versions
64 explicit affected versions
13 explicit affected versions
87 explicit affected versions
59 explicit affected versions
104 explicit affected versions
22 explicit affected versions
98 explicit affected versions
33 explicit affected versions
23 explicit affected versions
10 explicit affected versions
1 explicit affected versions
11 explicit affected versions
12 explicit affected versions
121 explicit affected versions
7 explicit affected versions
102 explicit affected versions
50 explicit affected versions
44 explicit affected versions
114 explicit affected versions
60 explicit affected versions
135 explicit affected versions
10 explicit affected versions
26 explicit affected versions
18 explicit affected versions
37 explicit affected versions
1 explicit affected versions
10 explicit affected versions
23 explicit affected versions
13 explicit affected versions
16 explicit affected versions
63 explicit affected versions
22 explicit affected versions
51 explicit affected versions
3 explicit affected versions
15 explicit affected versions
75 explicit affected versions
1 explicit affected versions
1 explicit affected versions
2 explicit affected versions
69 explicit affected versions
7 explicit affected versions
20 explicit affected versions
12 explicit affected versions
47 explicit affected versions
7 explicit affected versions
27 explicit affected versions
34 explicit affected versions
1 explicit affected versions
1 explicit affected versions
79 explicit affected versions
18 explicit affected versions
13 explicit affected versions
91 explicit affected versions
13 explicit affected versions
55 explicit affected versions
76 explicit affected versions
52 explicit affected versions
10 explicit affected versions
12 explicit affected versions
15 explicit affected versions
16 explicit affected versions
3 explicit affected versions
13 explicit affected versions
26 explicit affected versions
45 explicit affected versions
14 explicit affected versions
38 explicit affected versions
52 explicit affected versions
9 explicit affected versions
1 explicit affected versions
51 explicit affected versions
11 explicit affected versions
13 explicit affected versions
7 explicit affected versions
60 explicit affected versions
125 explicit affected versions
104 explicit affected versions
4 explicit affected versions
1 explicit affected versions
1 explicit affected versions
58 explicit affected versions
97 explicit affected versions
13 explicit affected versions
43 explicit affected versions
17 explicit affected versions
57 explicit affected versions
149 explicit affected versions
10 explicit affected versions
8 explicit affected versions
14 explicit affected versions
92 explicit affected versions
4 explicit affected versions
78 explicit affected versions
11 explicit affected versions
1 explicit affected versions
51 explicit affected versions
14 explicit affected versions
03 / CONNECTIONS
Connected vulnerabilities
04 / EVIDENCE
Source records
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.
05 / REFERENCES
Further evidence
- https://git.kernel.org/linus/b3a033e3ecd3471248d474ef263aadc0059e516a
- https://git.kernel.org/stable/c/1246d86e7bbde265761932c6e2dce28c69cdcb91
- https://git.kernel.org/stable/c/58c7f44c7b9e5ac7e3b1e5da2572ed7767a12f38
- https://git.kernel.org/stable/c/69548bb663fcb63f9ee0301be808a36b9d78dac3
- https://git.kernel.org/stable/c/9aa5d43ac4cace8fb9bd964ff6c23f599dc3cd24
- https://git.kernel.org/stable/c/a1686db1e59f8fc016c4c9361e2119dd206f479a
- https://git.kernel.org/stable/c/b3a033e3ecd3471248d474ef263aadc0059e516a
- https://git.kernel.org/stable/c/c72e0df0b56c1166736dc8eb62070ebb12591447
- https://git.kernel.org/stable/c/cc38c596e648575ce58bfc31623a6506eda4b94a
- https://ubuntu.com/security/CVE-2024-50229
- https://ubuntu.com/security/notices/USN-7276-1
- https://ubuntu.com/security/notices/USN-7277-1
- https://ubuntu.com/security/notices/USN-7288-1
- https://ubuntu.com/security/notices/USN-7288-2
- https://ubuntu.com/security/notices/USN-7289-1
- https://ubuntu.com/security/notices/USN-7289-2
- https://ubuntu.com/security/notices/USN-7289-3
- https://ubuntu.com/security/notices/USN-7289-4
- https://ubuntu.com/security/notices/USN-7291-1
- https://ubuntu.com/security/notices/USN-7293-1
- https://ubuntu.com/security/notices/USN-7294-1
- https://ubuntu.com/security/notices/USN-7294-2
- https://ubuntu.com/security/notices/USN-7294-3
- https://ubuntu.com/security/notices/USN-7294-4
- https://ubuntu.com/security/notices/USN-7295-1
- https://ubuntu.com/security/notices/USN-7305-1
- https://ubuntu.com/security/notices/USN-7308-1
- https://ubuntu.com/security/notices/USN-7310-1
- https://ubuntu.com/security/notices/USN-7331-1
- https://ubuntu.com/security/notices/USN-7342-1
- https://ubuntu.com/security/notices/USN-7344-1
- https://ubuntu.com/security/notices/USN-7344-2
- https://ubuntu.com/security/notices/USN-7383-1
- https://ubuntu.com/security/notices/USN-7383-2
- https://ubuntu.com/security/notices/USN-7384-1
- https://ubuntu.com/security/notices/USN-7384-2
- https://ubuntu.com/security/notices/USN-7385-1
- https://ubuntu.com/security/notices/USN-7386-1
- https://ubuntu.com/security/notices/USN-7388-1
- https://ubuntu.com/security/notices/USN-7389-1
- https://ubuntu.com/security/notices/USN-7390-1
- https://ubuntu.com/security/notices/USN-7393-1
- https://ubuntu.com/security/notices/USN-7401-1
- https://ubuntu.com/security/notices/USN-7403-1
- https://ubuntu.com/security/notices/USN-7413-1
- https://ubuntu.com/security/notices/USN-7451-1
- https://ubuntu.com/security/notices/USN-7458-1
- https://ubuntu.com/security/notices/USN-7468-1
- https://ubuntu.com/security/notices/USN-7523-1
- https://ubuntu.com/security/notices/USN-7524-1
- https://ubuntu.com/security/notices/USN-7539-1
- https://ubuntu.com/security/notices/USN-7540-1
- https://www.cve.org/CVERecord?id=CVE-2024-50229