UBUNTU-CVE-2021-47599
In the Linux kernel, the following vulnerability has been resolved: btrfs: use latest_dev in btrfs_show_devname The test case btrfs/238 reports the warning below: WARNING: CPU: 3 PID: 481 at fs/btrfs/super.c:2509 btrfs_show_devname+0x104/0x1e8 [btrfs] CPU: 2 PID: 1 Comm: systemd Tainted: G W O 5.14.0-rc1-custom #72 Hardware name: QEMU QEMU Virtual Machine, BIOS 0.0.0 02/06/2015 Call trace: btrfs_show_devname+0x108/0x1b4 [btrfs] show_mountinfo+0x234/0x2c4 m_show+0x28/0x34 seq_read_iter+0x12c/0x3c4 vfs_read+0x29c/0x2c8 ksys_read+0x80/0xec __arm64_sys_read+0x28/0x34 invoke_syscall+0x50/0xf8 do_el0_svc+0x88/0x138 el0_svc+0x2c/0x8c el0t_64_sync_handler+0x84/0xe4 el0t_64_sync+0x198/0x19c Reason: While btrfs_prepare_sprout() moves the fs_devices::devices into fs_devices::seed_list, the btrfs_show_devname() searches for the devices and found none, leading to the warning as in above. Fix: latest_dev is updated according to the changes to the device list. That means we could use the latest_dev->name to show the device name in /proc/self/mounts, the pointer will be always valid as it's assigned before the device is deleted from the list in remove or replace. The RCU protection is sufficient as the device structure is freed after synchronization.
02 / AFFECTED SOFTWARE
Affected packages
11 explicit affected versions
47 explicit affected versions
110 explicit affected versions
50 explicit affected versions
6 explicit affected versions
12 explicit affected versions
19 explicit affected versions
6 explicit affected versions
85 explicit affected versions
10 explicit affected versions
191 explicit affected versions
7 explicit affected versions
13 explicit affected versions
79 explicit affected versions
35 explicit affected versions
18 explicit affected versions
111 explicit affected versions
64 explicit affected versions
115 explicit affected versions
13 explicit affected versions
4 explicit affected versions
23 explicit affected versions
116 explicit affected versions
118 explicit affected versions
1 explicit affected versions
1 explicit affected versions
21 explicit affected versions
16 explicit affected versions
10 explicit affected versions
69 explicit affected versions
7 explicit affected versions
12 explicit affected versions
12 explicit affected versions
14 explicit affected versions
1 explicit affected versions
7 explicit affected versions
99 explicit affected versions
12 explicit affected versions
101 explicit affected versions
12 explicit affected versions
115 explicit affected versions
10 explicit affected versions
183 explicit affected versions
37 explicit affected versions
13 explicit affected versions
10 explicit affected versions
1 explicit affected versions
26 explicit affected versions
13 explicit affected versions
1 explicit affected versions
29 explicit affected versions
105 explicit affected versions
13 explicit affected versions
1 explicit affected versions
96 explicit affected versions
33 explicit affected versions
23 explicit affected versions
10 explicit affected versions
109 explicit affected versions
11 explicit affected versions
12 explicit affected versions
132 explicit affected versions
7 explicit affected versions
12 explicit affected versions
2 explicit affected versions
124 explicit affected versions
160 explicit affected versions
146 explicit affected versions
10 explicit affected versions
26 explicit affected versions
13 explicit affected versions
132 explicit affected versions
73 explicit affected versions
16 explicit affected versions
3 explicit affected versions
126 explicit affected versions
86 explicit affected versions
1 explicit affected versions
51 explicit affected versions
85 explicit affected versions
12 explicit affected versions
27 explicit affected versions
115 explicit affected versions
1 explicit affected versions
1 explicit affected versions
90 explicit affected versions
8 explicit affected versions
5 explicit affected versions
8 explicit affected versions
1 explicit affected versions
10 explicit affected versions
13 explicit affected versions
104 explicit affected versions
13 explicit affected versions
66 explicit affected versions
7 explicit affected versions
87 explicit affected versions
10 explicit affected versions
12 explicit affected versions
103 explicit affected versions
75 explicit affected versions
50 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
14 explicit affected versions
38 explicit affected versions
9 explicit affected versions
11 explicit affected versions
7 explicit affected versions
92 explicit affected versions
136 explicit affected versions
115 explicit affected versions
4 explicit affected versions
106 explicit affected versions
13 explicit affected versions
43 explicit affected versions
71 explicit affected versions
139 explicit affected versions
113 explicit affected versions
160 explicit affected versions
10 explicit affected versions
8 explicit affected versions
83 explicit affected versions
14 explicit affected versions
4 explicit affected versions
78 explicit affected versions
11 explicit affected versions
1 explicit affected versions
62 explicit affected versions
117 explicit affected versions
03 / CONNECTIONS
Connected vulnerabilities
04 / EVIDENCE
Source records
In the Linux kernel, the following vulnerability has been resolved: btrfs: use latest_dev in btrfs_show_devname The test case btrfs/238 reports the warning below: WARNING: CPU: 3 PID: 481 at fs/btrfs/super.c:2509 btrfs_show_devname+0x104/0x1e8 [btrfs] CPU: 2 PID: 1 Comm: systemd Tainted: G W O 5.14.0-rc1-custom #72 Hardware name: QEMU QEMU Virtual Machine, BIOS 0.0.0 02/06/2015 Call trace: btrfs_show_devname+0x108/0x1b4 [btrfs] show_mountinfo+0x234/0x2c4 m_show+0x28/0x34 seq_read_iter+0x12c/0x3c4 vfs_read+0x29c/0x2c8 ksys_read+0x80/0xec __arm64_sys_read+0x28/0x34 invoke_syscall+0x50/0xf8 do_el0_svc+0x88/0x138 el0_svc+0x2c/0x8c el0t_64_sync_handler+0x84/0xe4 el0t_64_sync+0x198/0x19c Reason: While btrfs_prepare_sprout() moves the fs_devices::devices into fs_devices::seed_list, the btrfs_show_devname() searches for the devices and found none, leading to the warning as in above. Fix: latest_dev is updated according to the changes to the device list. That means we could use the latest_dev->name to show the device name in /proc/self/mounts, the pointer will be always valid as it's assigned before the device is deleted from the list in remove or replace. The RCU protection is sufficient as the device structure is freed after synchronization.
05 / REFERENCES
Further evidence
- https://git.kernel.org/linus/6605fd2f394bba0a0059df2b6cfc87b0b6d393a2
- https://git.kernel.org/stable/c/6605fd2f394bba0a0059df2b6cfc87b0b6d393a2
- https://git.kernel.org/stable/c/e342c2558016ead462f376b6c6c2ac5efc17f3b1
- https://ubuntu.com/security/CVE-2021-47599
- https://ubuntu.com/security/notices/USN-8070-1
- https://ubuntu.com/security/notices/USN-8070-2
- https://ubuntu.com/security/notices/USN-8070-3
- https://ubuntu.com/security/notices/USN-8098-1
- https://ubuntu.com/security/notices/USN-8098-10
- https://ubuntu.com/security/notices/USN-8098-2
- https://ubuntu.com/security/notices/USN-8098-3
- https://ubuntu.com/security/notices/USN-8098-4
- https://ubuntu.com/security/notices/USN-8098-5
- https://ubuntu.com/security/notices/USN-8098-6
- https://ubuntu.com/security/notices/USN-8098-7
- https://ubuntu.com/security/notices/USN-8098-8
- https://ubuntu.com/security/notices/USN-8098-9
- https://ubuntu.com/security/notices/USN-8107-1
- https://ubuntu.com/security/notices/USN-8112-1
- https://ubuntu.com/security/notices/USN-8112-2
- https://ubuntu.com/security/notices/USN-8112-3
- https://ubuntu.com/security/notices/USN-8112-4
- https://ubuntu.com/security/notices/USN-8112-5
- https://ubuntu.com/security/notices/USN-8201-1
- https://ubuntu.com/security/notices/USN-8224-1
- https://www.cve.org/CVERecord?id=CVE-2021-47599