https://vulnerability.circl.lu/sightings/feed 2026-05-09T03:55:20.945089+00:00 Vulnerability-Lookup info@circl.lu python-feedgen Contains only the most 10 recent sightings. https://vulnerability.circl.lu/sighting/80ff4d79-5e4b-4d1b-b84b-e09671c83efe/export 2026-05-09T03:55:21.329696+00:00 Automation user http://vulnerability.circl.lu/user/automation {"uuid": "80ff4d79-5e4b-4d1b-b84b-e09671c83efe", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2021-47343", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/14727", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2021-47343\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\ndm btree remove: assign new_root only when removal succeeds\n\nremove_raw() in dm_btree_remove() may fail due to IO read error\n(e.g. read the content of origin block fails during shadowing),\nand the value of shadow_spine::root is uninitialized, but\nthe uninitialized value is still assign to new_root in the\nend of dm_btree_remove().\n\nFor dm-thin, the value of pmd->details_root or pmd->root will become\nan uninitialized value, so if trying to read details_info tree again\nout-of-bound memory may occur as showed below:\n\n general protection fault, probably for non-canonical address 0x3fdcb14c8d7520\n CPU: 4 PID: 515 Comm: dmsetup Not tainted 5.13.0-rc6\n Hardware name: QEMU Standard PC\n RIP: 0010:metadata_ll_load_ie+0x14/0x30\n Call Trace:\n sm_metadata_count_is_more_than_one+0xb9/0xe0\n dm_tm_shadow_block+0x52/0x1c0\n shadow_step+0x59/0xf0\n remove_raw+0xb2/0x170\n dm_btree_remove+0xf4/0x1c0\n dm_pool_delete_thin_device+0xc3/0x140\n pool_message+0x218/0x2b0\n target_message+0x251/0x290\n ctl_ioctl+0x1c4/0x4d0\n dm_ctl_ioctl+0xe/0x20\n __x64_sys_ioctl+0x7b/0xb0\n do_syscall_64+0x40/0xb0\n entry_SYSCALL_64_after_hwframe+0x44/0xae\n\nFixing it by only assign new_root when removal succeeds\n\ud83d\udccf Published: 2024-05-21T14:35:50.293Z\n\ud83d\udccf Modified: 2025-05-04T07:09:01.476Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/4c84b3e0728ffe10d89c633694c35a02b5c477dc\n2. https://git.kernel.org/stable/c/c154775619186781aaf8a99333ac07437a1768d5\n3. https://git.kernel.org/stable/c/73f27adaa73e3057a9ec464e33c4f54d34ea5de3\n4. https://git.kernel.org/stable/c/8fbae4a1bdb5b889490cdee929e68540151536e5\n5. https://git.kernel.org/stable/c/964d57d1962d7e68f0f578f05d9ae4a104d74851\n6. https://git.kernel.org/stable/c/ba47e65a5de3e0e8270301a409fc63d3129fdb9e\n7. https://git.kernel.org/stable/c/89bf942314b78d454db92427201421b5dec132d9\n8. https://git.kernel.org/stable/c/ad365e9351ac2b450e7e79932ff6abf59342d91a\n9. https://git.kernel.org/stable/c/b6e58b5466b2959f83034bead2e2e1395cca8aeb", "creation_timestamp": "2025-05-04T07:18:06.000000Z"} 2025-05-04T07:18:06+00:00