cbcvebase.
CVE-2021-47189
published 2024-04-10

CVE-2021-47189: In the Linux kernel, the following vulnerability has been resolved: btrfs: fix memory ordering between normal and ordered work functions Ordered work functions…

PriorityP434medium6.3CVSS 3.1
AVNACLPRLUINSUCLILAL
EPSS
0.92%
56.8th percentile
In the Linux kernel, the following vulnerability has been resolved: btrfs: fix memory ordering between normal and ordered work functions Ordered work functions aren't guaranteed to be handled by the same thread which executed the normal work functions. The only way execution between normal/ordered functions is synchronized is via the WORK_DONE_BIT, unfortunately the used bitops don't guarantee any ordering whatsoever. This manifested as seemingly inexplicable crashes on ARM64, where async_chunk::inode is seen as non-null in async_cow_submit which causes submit_compressed_extents to be called and crash occurs because async_chunk::inode suddenly became NULL. The call trace was similar to: pc : submit_compressed_extents+0x38/0x3d0 lr : async_cow_submit+0x50/0xd0 sp : ffff800015d4bc20 Call trace: submit_compressed_extents+0x38/0x3d0 async_cow_submit+0x50/0xd0 run_ordered_work+0xc8/0x280 btrfs_work_helper+0x98/0x250 process_one_work+0x1f0/0x4ac worker_thread+0x188/0x504 kthread+0x110/0x114 ret_from_fork+0x10/0x18 Fix this by adding respective barrier calls which ensure that all accesses preceding setting of WORK_DONE_BIT are strictly ordered before setting the flag. At the same time add a read barrier after reading of WORK_DONE_BIT in run_ordered_work which ensures all subsequent loads would be strictly ordered after reading the bit. This in turn ensures are all accesses before WORK_DONE_BIT are going to be strictly ordered before any access that can occur in ordered_func.

Affected

22 ranges
VendorProductVersion rangeFixed in
debianlinux< linux 5.15.5-1 (bookworm)linux 5.15.5-1 (bookworm)
linuxlinux——
linuxlinux>= 08a9ff3264181986d1d692a4e6fce3669700c9f8 < bd660a20fea3ec60a49709ef5360f145ec0fe779bd660a20fea3ec60a49709ef5360f145ec0fe779
linuxlinux>= 08a9ff3264181986d1d692a4e6fce3669700c9f8 < 637d652d351fd4f263ef302dc52f3971d314e500637d652d351fd4f263ef302dc52f3971d314e500
linuxlinux>= 08a9ff3264181986d1d692a4e6fce3669700c9f8 < 804a9d239ae9cbe88e861a7cd62319cc6ec7b136804a9d239ae9cbe88e861a7cd62319cc6ec7b136
linuxlinux>= 08a9ff3264181986d1d692a4e6fce3669700c9f8 < ed058d735a70f4b063323f1a7bb33cda0f987513ed058d735a70f4b063323f1a7bb33cda0f987513
linuxlinux>= 08a9ff3264181986d1d692a4e6fce3669700c9f8 < 670f6b3867c8f0f11e5097f353b164cecfec6179670f6b3867c8f0f11e5097f353b164cecfec6179
linuxlinux>= 08a9ff3264181986d1d692a4e6fce3669700c9f8 < 6adbc07ebcaf8bead08b21687d49e0fc944009876adbc07ebcaf8bead08b21687d49e0fc94400987
linuxlinux>= 08a9ff3264181986d1d692a4e6fce3669700c9f8 < 47e6f9f69153247109042010f3a77579e9dc61ff47e6f9f69153247109042010f3a77579e9dc61ff
linuxlinux>= 08a9ff3264181986d1d692a4e6fce3669700c9f8 < 45da9c1767ac31857df572f0a909fbe88fd5a7e945da9c1767ac31857df572f0a909fbe88fd5a7e9
linuxlinux_kernel——
linuxlinux_kernel>= 0 < 5.10.84-15.10.84-1
linuxlinux_kernel>= 0 < 5.15.5-15.15.5-1
linuxlinux_kernel>= 0 < 5.15.5-15.15.5-1
linuxlinux_kernel>= 0 < 5.15.5-15.15.5-1
linuxlinux_kernel>= 3.15 < 4.4.2934.4.293
linuxlinux_kernel>= 4.10 < 4.14.2564.14.256
linuxlinux_kernel>= 4.15 < 4.19.2184.19.218
linuxlinux_kernel>= 4.20 < 5.4.1625.4.162
linuxlinux_kernel>= 4.5 < 4.9.2914.9.291
linuxlinux_kernel>= 5.11 < 5.15.55.15.5
linuxlinux_kernel>= 5.5 < 5.10.825.10.82

CVSS provenance

nvdv3.16.3MEDIUMCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L
osv6.3MEDIUM
vendor_debian6.3MEDIUM
vendor_redhat6.3MEDIUM
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.