UBUNTU-CVE-2025-40105
In the Linux kernel, the following vulnerability has been resolved: vfs: Don't leak disconnected dentries on umount When user calls open_by_handle_at() on some inode that is not cached, we will create disconnected dentry for it. If such dentry is a directory, exportfs_decode_fh_raw() will then try to connect this dentry to the dentry tree through reconnect_path(). It may happen for various reasons (such as corrupted fs or race with rename) that the call to lookup_one_unlocked() in reconnect_one() will fail to find the dentry we are trying to reconnect and instead create a new dentry under the parent. Now this dentry will not be marked as disconnected although the parent still may well be disconnected (at least in case this inconsistency happened because the fs is corrupted and .. doesn't point to the real parent directory). This creates inconsistency in disconnected flags but AFAICS it was mostly harmless. At least until commit f1ee616214cb ("VFS: don't keep disconnected dentries on d_anon") which removed adding of most disconnected dentries to sb->s_anon list. Thus after this commit cleanup of disconnected dentries implicitely relies on the fact that dput() will immediately reclaim such dentries. However when some leaf dentry isn't marked as disconnected, as in the scenario described above, the reclaim doesn't happen and the dentries are "leaked". Memory reclaim can eventually reclaim them but otherwise they stay in memory and if umount comes first, we hit infamous "Busy inodes after unmount" bug. Make sure all dentries created under a disconnected parent are marked as disconnected as well.
02 / AFFECTED SOFTWARE
Affected packages
11 explicit affected versions
53 explicit affected versions
116 explicit affected versions
78 explicit affected versions
50 explicit affected versions
6 explicit affected versions
12 explicit affected versions
19 explicit affected versions
10 explicit affected versions
6 explicit affected versions
88 explicit affected versions
24 explicit affected versions
73 explicit affected versions
73 explicit affected versions
91 explicit affected versions
79 explicit affected versions
68 explicit affected versions
10 explicit affected versions
30 explicit affected versions
26 explicit affected versions
80 explicit affected versions
7 explicit affected versions
77 explicit affected versions
34 explicit affected versions
13 explicit affected versions
37 explicit affected versions
35 explicit affected versions
40 explicit affected versions
38 explicit affected versions
18 explicit affected versions
35 explicit affected versions
64 explicit affected versions
39 explicit affected versions
120 explicit affected versions
13 explicit affected versions
4 explicit affected versions
23 explicit affected versions
45 explicit affected versions
124 explicit affected versions
1 explicit affected versions
21 explicit affected versions
9 explicit affected versions
16 explicit affected versions
10 explicit affected versions
12 explicit affected versions
76 explicit affected versions
41 explicit affected versions
8 explicit affected versions
7 explicit affected versions
12 explicit affected versions
11 explicit affected versions
7 explicit affected versions
12 explicit affected versions
14 explicit affected versions
10 explicit affected versions
1 explicit affected versions
7 explicit affected versions
9 explicit affected versions
104 explicit affected versions
12 explicit affected versions
1 explicit affected versions
105 explicit affected versions
12 explicit affected versions
34 explicit affected versions
34 explicit affected versions
16 explicit affected versions
9 explicit affected versions
23 explicit affected versions
27 explicit affected versions
10 explicit affected versions
37 explicit affected versions
10 explicit affected versions
1 explicit affected versions
13 explicit affected versions
33 explicit affected versions
3 explicit affected versions
10 explicit affected versions
11 explicit affected versions
55 explicit affected versions
1 explicit affected versions
26 explicit affected versions
5 explicit affected versions
13 explicit affected versions
27 explicit affected versions
29 explicit affected versions
111 explicit affected versions
13 explicit affected versions
12 explicit affected versions
85 explicit affected versions
34 explicit affected versions
34 explicit affected versions
100 explicit affected versions
80 explicit affected versions
43 explicit affected versions
33 explicit affected versions
23 explicit affected versions
49 explicit affected versions
10 explicit affected versions
13 explicit affected versions
12 explicit affected versions
11 explicit affected versions
5 explicit affected versions
12 explicit affected versions
1 explicit affected versions
7 explicit affected versions
12 explicit affected versions
8 explicit affected versions
5 explicit affected versions
65 explicit affected versions
81 explicit affected versions
10 explicit affected versions
26 explicit affected versions
32 explicit affected versions
1 explicit affected versions
57 explicit affected versions
28 explicit affected versions
40 explicit affected versions
11 explicit affected versions
1 explicit affected versions
13 explicit affected versions
39 explicit affected versions
78 explicit affected versions
16 explicit affected versions
79 explicit affected versions
43 explicit affected versions
3 explicit affected versions
132 explicit affected versions
1 explicit affected versions
7 explicit affected versions
2 explicit affected versions
7 explicit affected versions
51 explicit affected versions
8 explicit affected versions
18 explicit affected versions
35 explicit affected versions
12 explicit affected versions
66 explicit affected versions
68 explicit affected versions
1 explicit affected versions
27 explicit affected versions
54 explicit affected versions
121 explicit affected versions
1 explicit affected versions
36 explicit affected versions
8 explicit affected versions
45 explicit affected versions
5 explicit affected versions
8 explicit affected versions
1 explicit affected versions
10 explicit affected versions
7 explicit affected versions
39 explicit affected versions
13 explicit affected versions
110 explicit affected versions
13 explicit affected versions
72 explicit affected versions
7 explicit affected versions
8 explicit affected versions
10 explicit affected versions
12 explicit affected versions
9 explicit affected versions
28 explicit affected versions
108 explicit affected versions
80 explicit affected versions
56 explicit affected versions
44 explicit affected versions
16 explicit affected versions
3 explicit affected versions
13 explicit affected versions
26 explicit affected versions
45 explicit affected versions
37 explicit affected versions
44 explicit affected versions
14 explicit affected versions
38 explicit affected versions
9 explicit affected versions
9 explicit affected versions
11 explicit affected versions
32 explicit affected versions
15 explicit affected versions
6 explicit affected versions
81 explicit affected versions
8 explicit affected versions
7 explicit affected versions
4 explicit affected versions
70 explicit affected versions
1 explicit affected versions
1 explicit affected versions
1 explicit affected versions
79 explicit affected versions
70 explicit affected versions
69 explicit affected versions
13 explicit affected versions
43 explicit affected versions
77 explicit affected versions
6 explicit affected versions
119 explicit affected versions
10 explicit affected versions
8 explicit affected versions
38 explicit affected versions
88 explicit affected versions
14 explicit affected versions
4 explicit affected versions
78 explicit affected versions
6 explicit affected versions
11 explicit affected versions
1 explicit affected versions
123 explicit affected versions
12 explicit affected versions
32 explicit affected versions
69 explicit affected versions
03 / CONNECTIONS
Connected vulnerabilities
04 / EVIDENCE
Source records
In the Linux kernel, the following vulnerability has been resolved: vfs: Don't leak disconnected dentries on umount When user calls open_by_handle_at() on some inode that is not cached, we will create disconnected dentry for it. If such dentry is a directory, exportfs_decode_fh_raw() will then try to connect this dentry to the dentry tree through reconnect_path(). It may happen for various reasons (such as corrupted fs or race with rename) that the call to lookup_one_unlocked() in reconnect_one() will fail to find the dentry we are trying to reconnect and instead create a new dentry under the parent. Now this dentry will not be marked as disconnected although the parent still may well be disconnected (at least in case this inconsistency happened because the fs is corrupted and .. doesn't point to the real parent directory). This creates inconsistency in disconnected flags but AFAICS it was mostly harmless. At least until commit f1ee616214cb ("VFS: don't keep disconnected dentries on d_anon") which removed adding of most disconnected dentries to sb->s_anon list. Thus after this commit cleanup of disconnected dentries implicitely relies on the fact that dput() will immediately reclaim such dentries. However when some leaf dentry isn't marked as disconnected, as in the scenario described above, the reclaim doesn't happen and the dentries are "leaked". Memory reclaim can eventually reclaim them but otherwise they stay in memory and if umount comes first, we hit infamous "Busy inodes after unmount" bug. Make sure all dentries created under a disconnected parent are marked as disconnected as well.
05 / REFERENCES
Further evidence
- https://git.kernel.org/linus/56094ad3eaa21e6621396cc33811d8f72847a834
- https://git.kernel.org/stable/c/20863bb7fbb016379f8227122edfabc5c799bc79
- https://git.kernel.org/stable/c/56094ad3eaa21e6621396cc33811d8f72847a834
- https://git.kernel.org/stable/c/620f3b0ede9c5cb4976cd0457d0b04ad551e5d6b
- https://git.kernel.org/stable/c/7e0c8aaf4e28918abded547a5147c7d52c4af7d2
- https://git.kernel.org/stable/c/8004d4b8cbf1bd68a23c160d57287e177c82cc69
- https://git.kernel.org/stable/c/b5abafd0aa8d7bcb935c8f91e4cfc2f2820759e4
- https://git.kernel.org/stable/c/cebfbf40056a4d858b2a3ca59a69936d599bd209
- https://git.kernel.org/stable/c/eadc49999fa994d6fbd70c332bd5d5051cc42261
- https://ubuntu.com/security/CVE-2025-40105
- https://ubuntu.com/security/notices/USN-8029-1
- https://ubuntu.com/security/notices/USN-8029-2
- https://ubuntu.com/security/notices/USN-8029-3
- https://ubuntu.com/security/notices/USN-8030-1
- https://ubuntu.com/security/notices/USN-8033-1
- https://ubuntu.com/security/notices/USN-8033-2
- https://ubuntu.com/security/notices/USN-8033-3
- https://ubuntu.com/security/notices/USN-8033-4
- https://ubuntu.com/security/notices/USN-8033-5
- https://ubuntu.com/security/notices/USN-8033-6
- https://ubuntu.com/security/notices/USN-8033-7
- https://ubuntu.com/security/notices/USN-8033-8
- https://ubuntu.com/security/notices/USN-8034-1
- https://ubuntu.com/security/notices/USN-8034-2
- https://ubuntu.com/security/notices/USN-8048-1
- https://ubuntu.com/security/notices/USN-8095-1
- https://ubuntu.com/security/notices/USN-8095-2
- https://ubuntu.com/security/notices/USN-8095-3
- https://ubuntu.com/security/notices/USN-8095-4
- https://ubuntu.com/security/notices/USN-8095-5
- https://ubuntu.com/security/notices/USN-8100-1
- https://ubuntu.com/security/notices/USN-8125-1
- https://ubuntu.com/security/notices/USN-8126-1
- https://ubuntu.com/security/notices/USN-8141-1
- https://ubuntu.com/security/notices/USN-8163-1
- https://ubuntu.com/security/notices/USN-8163-2
- https://ubuntu.com/security/notices/USN-8165-1
- https://ubuntu.com/security/notices/USN-8243-1
- https://ubuntu.com/security/notices/USN-8261-1
- https://www.cve.org/CVERecord?id=CVE-2025-40105