UBUNTU-CVE-2021-47145
In the Linux kernel, the following vulnerability has been resolved: btrfs: do not BUG_ON in link_to_fixup_dir While doing error injection testing I got the following panic kernel BUG at fs/btrfs/tree-log.c:1862! invalid opcode: 0000 [#1] SMP NOPTI CPU: 1 PID: 7836 Comm: mount Not tainted 5.13.0-rc1+ #305 Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.13.0-2.fc32 04/01/2014 RIP: 0010:link_to_fixup_dir+0xd5/0xe0 RSP: 0018:ffffb5800180fa30 EFLAGS: 00010216 RAX: fffffffffffffffb RBX: 00000000fffffffb RCX: ffff8f595287faf0 RDX: ffffb5800180fa37 RSI: ffff8f5954978800 RDI: 0000000000000000 RBP: ffff8f5953af9450 R08: 0000000000000019 R09: 0000000000000001 R10: 000151f408682970 R11: 0000000120021001 R12: ffff8f5954978800 R13: ffff8f595287faf0 R14: ffff8f5953c77dd0 R15: 0000000000000065 FS: 00007fc5284c8c40(0000) GS:ffff8f59bbd00000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007fc5287f47c0 CR3: 000000011275e002 CR4: 0000000000370ee0 Call Trace: replay_one_buffer+0x409/0x470 ? btree_read_extent_buffer_pages+0xd0/0x110 walk_up_log_tree+0x157/0x1e0 walk_log_tree+0xa6/0x1d0 btrfs_recover_log_trees+0x1da/0x360 ? replay_one_extent+0x7b0/0x7b0 open_ctree+0x1486/0x1720 btrfs_mount_root.cold+0x12/0xea ? __kmalloc_track_caller+0x12f/0x240 legacy_get_tree+0x24/0x40 vfs_get_tree+0x22/0xb0 vfs_kern_mount.part.0+0x71/0xb0 btrfs_mount+0x10d/0x380 ? vfs_parse_fs_string+0x4d/0x90 legacy_get_tree+0x24/0x40 vfs_get_tree+0x22/0xb0 path_mount+0x433/0xa10 __x64_sys_mount+0xe3/0x120 do_syscall_64+0x3d/0x80 entry_SYSCALL_64_after_hwframe+0x44/0xae We can get -EIO or any number of legitimate errors from btrfs_search_slot(), panicing here is not the appropriate response. The error path for this code handles errors properly, simply return the error.
02 / AFFECTED SOFTWARE
Affected packages
50 explicit affected versions
6 explicit affected versions
12 explicit affected versions
6 explicit affected versions
57 explicit affected versions
2 explicit affected versions
191 explicit affected versions
7 explicit affected versions
67 explicit affected versions
28 explicit affected versions
47 explicit affected versions
20 explicit affected versions
35 explicit affected versions
18 explicit affected versions
77 explicit affected versions
13 explicit affected versions
4 explicit affected versions
23 explicit affected versions
117 explicit affected versions
1 explicit affected versions
1 explicit affected versions
21 explicit affected versions
16 explicit affected versions
10 explicit affected versions
1 explicit affected versions
7 explicit affected versions
12 explicit affected versions
12 explicit affected versions
1 explicit affected versions
7 explicit affected versions
12 explicit affected versions
30 explicit affected versions
38 explicit affected versions
12 explicit affected versions
30 explicit affected versions
116 explicit affected versions
22 explicit affected versions
10 explicit affected versions
184 explicit affected versions
37 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
13 explicit affected versions
61 explicit affected versions
1 explicit affected versions
33 explicit affected versions
33 explicit affected versions
23 explicit affected versions
10 explicit affected versions
46 explicit affected versions
11 explicit affected versions
12 explicit affected versions
69 explicit affected versions
7 explicit affected versions
12 explicit affected versions
31 explicit affected versions
2 explicit affected versions
161 explicit affected versions
26 explicit affected versions
10 explicit affected versions
26 explicit affected versions
13 explicit affected versions
16 explicit affected versions
3 explicit affected versions
1 explicit affected versions
51 explicit affected versions
23 explicit affected versions
12 explicit affected versions
27 explicit affected versions
1 explicit affected versions
1 explicit affected versions
26 explicit affected versions
8 explicit affected versions
5 explicit affected versions
20 explicit affected versions
8 explicit affected versions
1 explicit affected versions
21 explicit affected versions
10 explicit affected versions
13 explicit affected versions
1 explicit affected versions
7 explicit affected versions
23 explicit affected versions
10 explicit affected versions
12 explicit affected versions
19 explicit affected versions
44 explicit affected versions
16 explicit affected versions
3 explicit affected versions
13 explicit affected versions
26 explicit affected versions
37 explicit affected versions
38 explicit affected versions
9 explicit affected versions
11 explicit affected versions
21 explicit affected versions
7 explicit affected versions
93 explicit affected versions
4 explicit affected versions
77 explicit affected versions
54 explicit affected versions
4 explicit affected versions
45 explicit affected versions
20 explicit affected versions
43 explicit affected versions
1 explicit affected versions
140 explicit affected versions
92 explicit affected versions
10 explicit affected versions
8 explicit affected versions
14 explicit affected versions
23 explicit affected versions
4 explicit affected versions
10 explicit affected versions
1 explicit affected versions
1 explicit affected versions
03 / CONNECTIONS
Connected vulnerabilities
04 / EVIDENCE
Source records
In the Linux kernel, the following vulnerability has been resolved: btrfs: do not BUG_ON in link_to_fixup_dir While doing error injection testing I got the following panic kernel BUG at fs/btrfs/tree-log.c:1862! invalid opcode: 0000 [#1] SMP NOPTI CPU: 1 PID: 7836 Comm: mount Not tainted 5.13.0-rc1+ #305 Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.13.0-2.fc32 04/01/2014 RIP: 0010:link_to_fixup_dir+0xd5/0xe0 RSP: 0018:ffffb5800180fa30 EFLAGS: 00010216 RAX: fffffffffffffffb RBX: 00000000fffffffb RCX: ffff8f595287faf0 RDX: ffffb5800180fa37 RSI: ffff8f5954978800 RDI: 0000000000000000 RBP: ffff8f5953af9450 R08: 0000000000000019 R09: 0000000000000001 R10: 000151f408682970 R11: 0000000120021001 R12: ffff8f5954978800 R13: ffff8f595287faf0 R14: ffff8f5953c77dd0 R15: 0000000000000065 FS: 00007fc5284c8c40(0000) GS:ffff8f59bbd00000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007fc5287f47c0 CR3: 000000011275e002 CR4: 0000000000370ee0 Call Trace: replay_one_buffer+0x409/0x470 ? btree_read_extent_buffer_pages+0xd0/0x110 walk_up_log_tree+0x157/0x1e0 walk_log_tree+0xa6/0x1d0 btrfs_recover_log_trees+0x1da/0x360 ? replay_one_extent+0x7b0/0x7b0 open_ctree+0x1486/0x1720 btrfs_mount_root.cold+0x12/0xea ? __kmalloc_track_caller+0x12f/0x240 legacy_get_tree+0x24/0x40 vfs_get_tree+0x22/0xb0 vfs_kern_mount.part.0+0x71/0xb0 btrfs_mount+0x10d/0x380 ? vfs_parse_fs_string+0x4d/0x90 legacy_get_tree+0x24/0x40 vfs_get_tree+0x22/0xb0 path_mount+0x433/0xa10 __x64_sys_mount+0xe3/0x120 do_syscall_64+0x3d/0x80 entry_SYSCALL_64_after_hwframe+0x44/0xae We can get -EIO or any number of legitimate errors from btrfs_search_slot(), panicing here is not the appropriate response. The error path for this code handles errors properly, simply return the error.
05 / REFERENCES
Further evidence
- https://git.kernel.org/stable/c/0eaf383c6a4a83c09f60fd07a1bea9f1a9181611
- https://git.kernel.org/stable/c/0ed102453aa1cd12fefde8f6b60b9519b0b1f003
- https://git.kernel.org/stable/c/6eccfb28f8dca70c9b1b3bb3194ca54cbe73a9fa
- https://git.kernel.org/stable/c/76bfd8ac20bebeae599452a03dfc5724c0475dcf
- https://git.kernel.org/stable/c/7e13db503918820e6333811cdc6f151dcea5090a
- https://git.kernel.org/stable/c/91df99a6eb50d5a1bc70fff4a09a0b7ae6aab96d
- https://git.kernel.org/stable/c/b545442133580dcb2f2496133bf850824d41255c
- https://git.kernel.org/stable/c/e934c4ee17b33bafb0444f2f9766cda7166d3c40
- https://ubuntu.com/security/CVE-2021-47145
- https://ubuntu.com/security/notices/USN-8143-1
- https://ubuntu.com/security/notices/USN-8143-2
- https://www.cve.org/CVERecord?id=CVE-2021-47145