CVE-2021-47343
published 2024-05-21CVE-2021-47343: In the Linux kernel, the following vulnerability has been resolved: dm btree remove: assign new_root only when removal succeeds remove_raw() in…
PriorityP420medium5.5CVSS 3.1
AVLACLPRLUINSUCNINAH
EPSS
0.27%
18.7th percentile
In the Linux kernel, the following vulnerability has been resolved:
dm btree remove: assign new_root only when removal succeeds
remove_raw() in dm_btree_remove() may fail due to IO read error
(e.g. read the content of origin block fails during shadowing),
and the value of shadow_spine::root is uninitialized, but
the uninitialized value is still assign to new_root in the
end of dm_btree_remove().
For dm-thin, the value of pmd->details_root or pmd->root will become
an uninitialized value, so if trying to read details_info tree again
out-of-bound memory may occur as showed below:
general protection fault, probably for non-canonical address 0x3fdcb14c8d7520
CPU: 4 PID: 515 Comm: dmsetup Not tainted 5.13.0-rc6
Hardware name: QEMU Standard PC
RIP: 0010:metadata_ll_load_ie+0x14/0x30
Call Trace:
sm_metadata_count_is_more_than_one+0xb9/0xe0
dm_tm_shadow_block+0x52/0x1c0
shadow_step+0x59/0xf0
remove_raw+0xb2/0x170
dm_btree_remove+0xf4/0x1c0
dm_pool_delete_thin_device+0xc3/0x140
pool_message+0x218/0x2b0
target_message+0x251/0x290
ctl_ioctl+0x1c4/0x4d0
dm_ctl_ioctl+0xe/0x20
__x64_sys_ioctl+0x7b/0xb0
do_syscall_64+0x40/0xb0
entry_SYSCALL_64_after_hwframe+0x44/0xae
Fixing it by only assign new_root when removal succeeds
Affected
23 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| debian | linux | < linux 5.14.6-1 (bookworm) | linux 5.14.6-1 (bookworm) |
| linux | linux | — | — |
| linux | linux | >= 3241b1d3e0aaafbfcd320f4d71ade629728cc4f4 < 4c84b3e0728ffe10d89c633694c35a02b5c477dc | 4c84b3e0728ffe10d89c633694c35a02b5c477dc |
| linux | linux | >= 3241b1d3e0aaafbfcd320f4d71ade629728cc4f4 < c154775619186781aaf8a99333ac07437a1768d5 | c154775619186781aaf8a99333ac07437a1768d5 |
| linux | linux | >= 3241b1d3e0aaafbfcd320f4d71ade629728cc4f4 < 73f27adaa73e3057a9ec464e33c4f54d34ea5de3 | 73f27adaa73e3057a9ec464e33c4f54d34ea5de3 |
| linux | linux | >= 3241b1d3e0aaafbfcd320f4d71ade629728cc4f4 < 8fbae4a1bdb5b889490cdee929e68540151536e5 | 8fbae4a1bdb5b889490cdee929e68540151536e5 |
| linux | linux | >= 3241b1d3e0aaafbfcd320f4d71ade629728cc4f4 < 964d57d1962d7e68f0f578f05d9ae4a104d74851 | 964d57d1962d7e68f0f578f05d9ae4a104d74851 |
| linux | linux | >= 3241b1d3e0aaafbfcd320f4d71ade629728cc4f4 < ba47e65a5de3e0e8270301a409fc63d3129fdb9e | ba47e65a5de3e0e8270301a409fc63d3129fdb9e |
| linux | linux | >= 3241b1d3e0aaafbfcd320f4d71ade629728cc4f4 < 89bf942314b78d454db92427201421b5dec132d9 | 89bf942314b78d454db92427201421b5dec132d9 |
| linux | linux | >= 3241b1d3e0aaafbfcd320f4d71ade629728cc4f4 < ad365e9351ac2b450e7e79932ff6abf59342d91a | ad365e9351ac2b450e7e79932ff6abf59342d91a |
| linux | linux | >= 3241b1d3e0aaafbfcd320f4d71ade629728cc4f4 < b6e58b5466b2959f83034bead2e2e1395cca8aeb | b6e58b5466b2959f83034bead2e2e1395cca8aeb |
| linux | linux_kernel | < 4.4.276 | 4.4.276 |
| linux | linux_kernel | >= 0 < 5.10.70-1 | 5.10.70-1 |
| linux | linux_kernel | >= 0 < 5.14.6-1 | 5.14.6-1 |
| linux | linux_kernel | >= 0 < 5.14.6-1 | 5.14.6-1 |
| linux | linux_kernel | >= 0 < 5.14.6-1 | 5.14.6-1 |
| linux | linux_kernel | >= 4.10 < 4.14.240 | 4.14.240 |
| linux | linux_kernel | >= 4.15 < 4.19.198 | 4.19.198 |
| linux | linux_kernel | >= 4.20 < 5.4.133 | 5.4.133 |
| linux | linux_kernel | >= 4.5 < 4.9.276 | 4.9.276 |
| linux | linux_kernel | >= 5.11 < 5.12.18 | 5.12.18 |
| linux | linux_kernel | >= 5.13 < 5.13.3 | 5.13.3 |
| linux | linux_kernel | >= 5.5 < 5.10.51 | 5.10.51 |
CVSS provenance
nvdv3.15.5MEDIUMCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
osv5.5MEDIUM
vendor_debian5.5MEDIUM
vendor_redhat5.5MEDIUM
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
Red Hat
kernel: dm btree remove: assign new_root only when removal succeeds
vendor_redhat·2024-05-21·CVSS 5.5
CVE-2021-47343 [MEDIUM] CWE-824 kernel: dm btree remove: assign new_root only when removal succeeds
kernel: dm btree remove: assign new_root only when removal succeeds
In the Linux kernel, the following vulnerability has been resolved:
dm btree remove: assign new_root only when removal succeeds
remove_raw() in dm_btree_remove() may fail due to IO read error
(e.g. read the content of origin block fails during shadowing),
and the value of shadow_spine::root is uninitialized, but
the uninitialized value is still assign to new_root in the
end of dm_btree_remove().
For dm-thin, the value of pmd->details_root or pmd->root will become
an uninitialized value, so if trying to read details_info tree again
out-of-bound memory may occur as showed below:
general protection fault, probably for non-canonical address 0x3fdcb14c8d7520
CPU: 4 PID: 515 Comm: dmsetup Not tainted 5.13.0-rc6
Hardware name: Q
Debian
CVE-2021-47343: linux - In the Linux kernel, the following vulnerability has been resolved: dm btree re...
vendor_debian·2021·CVSS 5.5
CVE-2021-47343 [MEDIUM] CVE-2021-47343: linux - In the Linux kernel, the following vulnerability has been resolved: dm btree re...
In the Linux kernel, the following vulnerability has been resolved: dm btree remove: assign new_root only when removal succeeds remove_raw() in dm_btree_remove() may fail due to IO read error (e.g. read the content of origin block fails during shadowing), and the value of shadow_spine::root is uninitialized, but the uninitialized value is still assign to new_root in the end of dm_btree_remove(). For dm-thin, the value of pmd->details_root or pmd->root will become an uninitialized value, so if trying to read details_info tree again out-of-bound memory may occur as showed below: general protection fault, probably for non-canonical address 0x3fdcb14c8d7520 CPU: 4 PID: 515 Comm: dmsetup Not tainted 5.13.0-rc6 Hardware name: QEMU Standard PC RIP: 0010:metadata_ll_load_ie+0x14/0x30 Call Trace: s
OSV
CVE-2021-47343: In the Linux kernel, the following vulnerability has been resolved: dm btree remove: assign new_root only when removal succeeds remove_raw() in dm_btr
osv·2024-05-21·CVSS 5.5
CVE-2021-47343 [MEDIUM] CVE-2021-47343: In the Linux kernel, the following vulnerability has been resolved: dm btree remove: assign new_root only when removal succeeds remove_raw() in dm_btr
In the Linux kernel, the following vulnerability has been resolved: dm btree remove: assign new_root only when removal succeeds remove_raw() in dm_btree_remove() may fail due to IO read error (e.g. read the content of origin block fails during shadowing), and the value of shadow_spine::root is uninitialized, but the uninitialized value is still assign to new_root in the end of dm_btree_remove(). For dm-thin, the value of pmd->details_root or pmd->root will become an uninitialized value, so if trying to read details_info tree again out-of-bound memory may occur as showed below: general protection fault, probably for non-canonical address 0x3fdcb14c8d7520 CPU: 4 PID: 515 Comm: dmsetup Not tainted 5.13.0-rc6 Hardware name: QEMU Standard PC RIP: 0010:metadata_ll_load_ie+0x14/0x30 Call Trace: s
GHSA
GHSA-qvgm-cw57-rm8q: In the Linux kernel, the following vulnerability has been resolved:
dm btree remove: assign new_root only when removal succeeds
remove_raw() in dm_b
ghsa_unreviewed·2024-05-21
CVE-2021-47343 [MEDIUM] CWE-1188 GHSA-qvgm-cw57-rm8q: In the Linux kernel, the following vulnerability has been resolved:
dm btree remove: assign new_root only when removal succeeds
remove_raw() in dm_b
In the Linux kernel, the following vulnerability has been resolved:
dm btree remove: assign new_root only when removal succeeds
remove_raw() in dm_btree_remove() may fail due to IO read error
(e.g. read the content of origin block fails during shadowing),
and the value of shadow_spine::root is uninitialized, but
the uninitialized value is still assign to new_root in the
end of dm_btree_remove().
For dm-thin, the value of pmd->details_root or pmd->root will become
an uninitialized value, so if trying to read details_info tree again
out-of-bound memory may occur as showed below:
general protection fault, probably for non-canonical address 0x3fdcb14c8d7520
CPU: 4 PID: 515 Comm: dmsetup Not tainted 5.13.0-rc6
Hardware name: QEMU Standard PC
RIP: 0010:metadata_ll_load_ie+0x14/0x30
Call Trac
No detection rules found.
No public exploits indexed.
https://git.kernel.org/stable/c/4c84b3e0728ffe10d89c633694c35a02b5c477dchttps://git.kernel.org/stable/c/73f27adaa73e3057a9ec464e33c4f54d34ea5de3https://git.kernel.org/stable/c/89bf942314b78d454db92427201421b5dec132d9https://git.kernel.org/stable/c/8fbae4a1bdb5b889490cdee929e68540151536e5https://git.kernel.org/stable/c/964d57d1962d7e68f0f578f05d9ae4a104d74851https://git.kernel.org/stable/c/ad365e9351ac2b450e7e79932ff6abf59342d91ahttps://git.kernel.org/stable/c/b6e58b5466b2959f83034bead2e2e1395cca8aebhttps://git.kernel.org/stable/c/ba47e65a5de3e0e8270301a409fc63d3129fdb9ehttps://git.kernel.org/stable/c/c154775619186781aaf8a99333ac07437a1768d5https://git.kernel.org/stable/c/4c84b3e0728ffe10d89c633694c35a02b5c477dchttps://git.kernel.org/stable/c/73f27adaa73e3057a9ec464e33c4f54d34ea5de3https://git.kernel.org/stable/c/89bf942314b78d454db92427201421b5dec132d9https://git.kernel.org/stable/c/8fbae4a1bdb5b889490cdee929e68540151536e5https://git.kernel.org/stable/c/964d57d1962d7e68f0f578f05d9ae4a104d74851https://git.kernel.org/stable/c/ad365e9351ac2b450e7e79932ff6abf59342d91ahttps://git.kernel.org/stable/c/b6e58b5466b2959f83034bead2e2e1395cca8aebhttps://git.kernel.org/stable/c/ba47e65a5de3e0e8270301a409fc63d3129fdb9ehttps://git.kernel.org/stable/c/c154775619186781aaf8a99333ac07437a1768d5
2024-05-21
Published