UBUNTU-CVE-2026-43472
In the Linux kernel, the following vulnerability has been resolved: unshare: fix unshare_fs() handling There's an unpleasant corner case in unshare(2), when we have a CLONE_NEWNS in flags and current->fs hadn't been shared at all; in that case copy_mnt_ns() gets passed current->fs instead of a private copy, which causes interesting warts in proof of correctness] > I guess if private means fs->users == 1, the condition could still be true. Unfortunately, it's worse than just a convoluted proof of correctness. Consider the case when we have CLONE_NEWCGROUP in addition to CLONE_NEWNS (and current->fs->users == 1). We pass current->fs to copy_mnt_ns(), all right. Suppose it succeeds and flips current->fs->{pwd,root} to corresponding locations in the new namespace. Now we proceed to copy_cgroup_ns(), which fails (e.g. with -ENOMEM). We call put_mnt_ns() on the namespace created by copy_mnt_ns(), it's destroyed and its mount tree is dissolved, but... current->fs->root and current->fs->pwd are both left pointing to now detached mounts. They are pinning those, so it's not a UAF, but it leaves the calling process with unshare(2) failing with -ENOMEM _and_ leaving it with pwd and root on detached isolated mounts. The last part is clearly a bug. There is other fun related to that mess (races with pivot_root(), including the one between pivot_root() and fork(), of all things), but this one is easy to isolate and fix - treat CLONE_NEWNS as "allocate a new fs_struct even if it hadn't been shared in the first place". Sure, we could go for something like "if both CLONE_NEWNS *and* one of the things that might end up failing after copy_mnt_ns() call in create_new_namespaces() are set, force allocation of new fs_struct", but let's keep it simple - the cost of copy_fs_struct() is trivial. Another benefit is that copy_mnt_ns() with CLONE_NEWNS *always* gets a freshly allocated fs_struct, yet to be attached to anything. That seriously simplifies the analysis... FWIW, that bug had been there since the introduction of unshare(2) ;-/
02 / AFFECTED SOFTWARE
Affected packages
11 explicit affected versions
6 explicit affected versions
53 explicit affected versions
10 explicit affected versions
6 explicit affected versions
85 explicit affected versions
116 explicit affected versions
87 explicit affected versions
50 explicit affected versions
6 explicit affected versions
12 explicit affected versions
19 explicit affected versions
97 explicit affected versions
59 explicit affected versions
24 explicit affected versions
82 explicit affected versions
83 explicit affected versions
91 explicit affected versions
84 explicit affected versions
76 explicit affected versions
10 explicit affected versions
37 explicit affected versions
26 explicit affected versions
89 explicit affected versions
191 explicit affected versions
7 explicit affected versions
84 explicit affected versions
40 explicit affected versions
13 explicit affected versions
10 explicit affected versions
44 explicit affected versions
35 explicit affected versions
49 explicit affected versions
47 explicit affected versions
18 explicit affected versions
40 explicit affected versions
118 explicit affected versions
62 explicit affected versions
45 explicit affected versions
120 explicit affected versions
13 explicit affected versions
4 explicit affected versions
121 explicit affected versions
23 explicit affected versions
52 explicit affected versions
124 explicit affected versions
1 explicit affected versions
1 explicit affected versions
21 explicit affected versions
7 explicit affected versions
16 explicit affected versions
10 explicit affected versions
20 explicit affected versions
76 explicit affected versions
77 explicit affected versions
48 explicit affected versions
8 explicit affected versions
7 explicit affected versions
12 explicit affected versions
11 explicit affected versions
111 explicit affected versions
7 explicit affected versions
12 explicit affected versions
14 explicit affected versions
10 explicit affected versions
105 explicit affected versions
1 explicit affected versions
7 explicit affected versions
17 explicit affected versions
104 explicit affected versions
12 explicit affected versions
12 explicit affected versions
41 explicit affected versions
120 explicit affected versions
43 explicit affected versions
16 explicit affected versions
17 explicit affected versions
27 explicit affected versions
34 explicit affected versions
10 explicit affected versions
37 explicit affected versions
10 explicit affected versions
11 explicit affected versions
13 explicit affected versions
39 explicit affected versions
3 explicit affected versions
10 explicit affected versions
11 explicit affected versions
65 explicit affected versions
1 explicit affected versions
26 explicit affected versions
10 explicit affected versions
13 explicit affected versions
144 explicit affected versions
34 explicit affected versions
95 explicit affected versions
1 explicit affected versions
29 explicit affected versions
111 explicit affected versions
13 explicit affected versions
12 explicit affected versions
41 explicit affected versions
40 explicit affected versions
8 explicit affected versions
1 explicit affected versions
100 explicit affected versions
89 explicit affected versions
52 explicit affected versions
33 explicit affected versions
23 explicit affected versions
54 explicit affected versions
58 explicit affected versions
10 explicit affected versions
20 explicit affected versions
188 explicit affected versions
19 explicit affected versions
7 explicit affected versions
11 explicit affected versions
5 explicit affected versions
12 explicit affected versions
11 explicit affected versions
5 explicit affected versions
12 explicit affected versions
10 explicit affected versions
16 explicit affected versions
138 explicit affected versions
2 explicit affected versions
10 explicit affected versions
74 explicit affected versions
132 explicit affected versions
90 explicit affected versions
165 explicit affected versions
154 explicit affected versions
26 explicit affected versions
39 explicit affected versions
1 explicit affected versions
66 explicit affected versions
46 explicit affected versions
35 explicit affected versions
48 explicit affected versions
11 explicit affected versions
10 explicit affected versions
13 explicit affected versions
139 explicit affected versions
78 explicit affected versions
16 explicit affected versions
88 explicit affected versions
1 explicit affected versions
50 explicit affected versions
116 explicit affected versions
3 explicit affected versions
132 explicit affected versions
93 explicit affected versions
7 explicit affected versions
2 explicit affected versions
15 explicit affected versions
51 explicit affected versions
16 explicit affected versions
92 explicit affected versions
18 explicit affected versions
43 explicit affected versions
12 explicit affected versions
70 explicit affected versions
7 explicit affected versions
27 explicit affected versions
63 explicit affected versions
121 explicit affected versions
1 explicit affected versions
1 explicit affected versions
98 explicit affected versions
43 explicit affected versions
8 explicit affected versions
5 explicit affected versions
8 explicit affected versions
8 explicit affected versions
1 explicit affected versions
10 explicit affected versions
7 explicit affected versions
46 explicit affected versions
13 explicit affected versions
110 explicit affected versions
13 explicit affected versions
72 explicit affected versions
7 explicit affected versions
140 explicit affected versions
94 explicit affected versions
10 explicit affected versions
12 explicit affected versions
9 explicit affected versions
36 explicit affected versions
108 explicit affected versions
80 explicit affected versions
56 explicit affected versions
44 explicit affected versions
37 explicit affected versions
16 explicit affected versions
3 explicit affected versions
13 explicit affected versions
26 explicit affected versions
45 explicit affected versions
50 explicit affected versions
14 explicit affected versions
38 explicit affected versions
167 explicit affected versions
4 explicit affected versions
9 explicit affected versions
17 explicit affected versions
11 explicit affected versions
39 explicit affected versions
18 explicit affected versions
14 explicit affected versions
88 explicit affected versions
90 explicit affected versions
6 explicit affected versions
7 explicit affected versions
97 explicit affected versions
121 explicit affected versions
79 explicit affected versions
10 explicit affected versions
1 explicit affected versions
1 explicit affected versions
1 explicit affected versions
78 explicit affected versions
78 explicit affected versions
13 explicit affected versions
43 explicit affected versions
77 explicit affected versions
16 explicit affected versions
119 explicit affected versions
10 explicit affected versions
8 explicit affected versions
45 explicit affected versions
88 explicit affected versions
14 explicit affected versions
4 explicit affected versions
78 explicit affected versions
14 explicit affected versions
11 explicit affected versions
1 explicit affected versions
69 explicit affected versions
123 explicit affected versions
19 explicit affected versions
39 explicit affected versions
77 explicit affected versions
03 / CONNECTIONS
Connected vulnerabilities
04 / EVIDENCE
Source records
In the Linux kernel, the following vulnerability has been resolved: unshare: fix unshare_fs() handling There's an unpleasant corner case in unshare(2), when we have a CLONE_NEWNS in flags and current->fs hadn't been shared at all; in that case copy_mnt_ns() gets passed current->fs instead of a private copy, which causes interesting warts in proof of correctness] > I guess if private means fs->users == 1, the condition could still be true. Unfortunately, it's worse than just a convoluted proof of correctness. Consider the case when we have CLONE_NEWCGROUP in addition to CLONE_NEWNS (and current->fs->users == 1). We pass current->fs to copy_mnt_ns(), all right. Suppose it succeeds and flips current->fs->{pwd,root} to corresponding locations in the new namespace. Now we proceed to copy_cgroup_ns(), which fails (e.g. with -ENOMEM). We call put_mnt_ns() on the namespace created by copy_mnt_ns(), it's destroyed and its mount tree is dissolved, but... current->fs->root and current->fs->pwd are both left pointing to now detached mounts. They are pinning those, so it's not a UAF, but it leaves the calling process with unshare(2) failing with -ENOMEM _and_ leaving it with pwd and root on detached isolated mounts. The last part is clearly a bug. There is other fun related to that mess (races with pivot_root(), including the one between pivot_root() and fork(), of all things), but this one is easy to isolate and fix - treat CLONE_NEWNS as "allocate a new fs_struct even if it hadn't been shared in the first place". Sure, we could go for something like "if both CLONE_NEWNS *and* one of the things that might end up failing after copy_mnt_ns() call in create_new_namespaces() are set, force allocation of new fs_struct", but let's keep it simple - the cost of copy_fs_struct() is trivial. Another benefit is that copy_mnt_ns() with CLONE_NEWNS *always* gets a freshly allocated fs_struct, yet to be attached to anything. That seriously simplifies the analysis... FWIW, that bug had been there since the introduction of unshare(2) ;-/
05 / REFERENCES
Further evidence
- https://git.kernel.org/linus/6c4b2243cb6c0755159bd567130d5e12e7b10d9f
- https://git.kernel.org/stable/c/42e21e74061b0ebbd859839f81acf10efad02a27
- https://git.kernel.org/stable/c/6c4b2243cb6c0755159bd567130d5e12e7b10d9f
- https://git.kernel.org/stable/c/845bf3c6963a52096d0d3866e4a92db77a0c03d8
- https://git.kernel.org/stable/c/aa9ebc084505fb26dd90f4d7a249045aad152043
- https://git.kernel.org/stable/c/af8f4be3b68ac8caa41c8e5ead0eeaf5e85e42d0
- https://git.kernel.org/stable/c/d0d99f60538ddb4a62ccaac2168d8f448965f083
- https://git.kernel.org/stable/c/d3ffc8f13034af895531a02c30b1fe3a34b46432
- https://git.kernel.org/stable/c/d7963d6997fea86a6def242ac36198b86655f912
- https://ubuntu.com/security/CVE-2026-43472
- https://ubuntu.com/security/notices/USN-8567-1
- https://ubuntu.com/security/notices/USN-8574-1
- https://ubuntu.com/security/notices/USN-8574-2
- https://ubuntu.com/security/notices/USN-8574-3
- https://ubuntu.com/security/notices/USN-8575-1
- https://ubuntu.com/security/notices/USN-8575-2
- https://ubuntu.com/security/notices/USN-8575-3
- https://ubuntu.com/security/notices/USN-8576-1
- https://ubuntu.com/security/notices/USN-8576-2
- https://ubuntu.com/security/notices/USN-8595-1
- https://ubuntu.com/security/notices/USN-8595-2
- https://ubuntu.com/security/notices/USN-8595-3
- https://ubuntu.com/security/notices/USN-8596-1
- https://ubuntu.com/security/notices/USN-8597-1
- https://ubuntu.com/security/notices/USN-8606-1
- https://ubuntu.com/security/notices/USN-8607-1
- https://ubuntu.com/security/notices/USN-8608-1
- https://ubuntu.com/security/notices/USN-8609-1
- https://ubuntu.com/security/notices/USN-8610-1
- https://ubuntu.com/security/notices/USN-8619-1
- https://ubuntu.com/security/notices/USN-8620-1
- https://ubuntu.com/security/notices/USN-8620-2
- https://ubuntu.com/security/notices/USN-8620-3
- https://ubuntu.com/security/notices/USN-8620-4
- https://www.cve.org/CVERecord?id=CVE-2026-43472