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 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 <registers omitted for brevity> 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.
Configurations

Configuration 1 (hide)

OR cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:5.16:rc1:*:*:*:*:*:*

History

30 Apr 2025, 16:34

Type Values Removed Values Added
References () https://git.kernel.org/stable/c/45da9c1767ac31857df572f0a909fbe88fd5a7e9 - () https://git.kernel.org/stable/c/45da9c1767ac31857df572f0a909fbe88fd5a7e9 - Patch
References () https://git.kernel.org/stable/c/47e6f9f69153247109042010f3a77579e9dc61ff - () https://git.kernel.org/stable/c/47e6f9f69153247109042010f3a77579e9dc61ff - Patch
References () https://git.kernel.org/stable/c/637d652d351fd4f263ef302dc52f3971d314e500 - () https://git.kernel.org/stable/c/637d652d351fd4f263ef302dc52f3971d314e500 - Patch
References () https://git.kernel.org/stable/c/670f6b3867c8f0f11e5097f353b164cecfec6179 - () https://git.kernel.org/stable/c/670f6b3867c8f0f11e5097f353b164cecfec6179 - Patch
References () https://git.kernel.org/stable/c/6adbc07ebcaf8bead08b21687d49e0fc94400987 - () https://git.kernel.org/stable/c/6adbc07ebcaf8bead08b21687d49e0fc94400987 - Patch
References () https://git.kernel.org/stable/c/804a9d239ae9cbe88e861a7cd62319cc6ec7b136 - () https://git.kernel.org/stable/c/804a9d239ae9cbe88e861a7cd62319cc6ec7b136 - Patch
References () https://git.kernel.org/stable/c/bd660a20fea3ec60a49709ef5360f145ec0fe779 - () https://git.kernel.org/stable/c/bd660a20fea3ec60a49709ef5360f145ec0fe779 - Patch
References () https://git.kernel.org/stable/c/ed058d735a70f4b063323f1a7bb33cda0f987513 - () https://git.kernel.org/stable/c/ed058d735a70f4b063323f1a7bb33cda0f987513 - Patch
CPE cpe:2.3:o:linux:linux_kernel:5.16:rc1:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
First Time Linux linux Kernel
Linux
CWE NVD-CWE-noinfo

21 Nov 2024, 06:35

Type Values Removed Values Added
References () https://git.kernel.org/stable/c/45da9c1767ac31857df572f0a909fbe88fd5a7e9 - () https://git.kernel.org/stable/c/45da9c1767ac31857df572f0a909fbe88fd5a7e9 -
References () https://git.kernel.org/stable/c/47e6f9f69153247109042010f3a77579e9dc61ff - () https://git.kernel.org/stable/c/47e6f9f69153247109042010f3a77579e9dc61ff -
References () https://git.kernel.org/stable/c/637d652d351fd4f263ef302dc52f3971d314e500 - () https://git.kernel.org/stable/c/637d652d351fd4f263ef302dc52f3971d314e500 -
References () https://git.kernel.org/stable/c/670f6b3867c8f0f11e5097f353b164cecfec6179 - () https://git.kernel.org/stable/c/670f6b3867c8f0f11e5097f353b164cecfec6179 -
References () https://git.kernel.org/stable/c/6adbc07ebcaf8bead08b21687d49e0fc94400987 - () https://git.kernel.org/stable/c/6adbc07ebcaf8bead08b21687d49e0fc94400987 -
References () https://git.kernel.org/stable/c/804a9d239ae9cbe88e861a7cd62319cc6ec7b136 - () https://git.kernel.org/stable/c/804a9d239ae9cbe88e861a7cd62319cc6ec7b136 -
References () https://git.kernel.org/stable/c/bd660a20fea3ec60a49709ef5360f145ec0fe779 - () https://git.kernel.org/stable/c/bd660a20fea3ec60a49709ef5360f145ec0fe779 -
References () https://git.kernel.org/stable/c/ed058d735a70f4b063323f1a7bb33cda0f987513 - () https://git.kernel.org/stable/c/ed058d735a70f4b063323f1a7bb33cda0f987513 -

01 Nov 2024, 18:35

Type Values Removed Values Added
CVSS v2 : unknown
v3 : unknown
v2 : unknown
v3 : 6.3
Summary
  • (es) En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: btrfs: arreglo del ordenamiento de memoria entre funciones de trabajo normales y ordenadas No se garantiza que las funciones de trabajo ordenadas sean manejadas por el mismo hilo que ejecutó las funciones de trabajo normales. La única forma de sincronizar la ejecución entre funciones normales/ordenadas es a través de WORK_DONE_BIT, desafortunadamente los bitops utilizados no garantizan ningún orden. Esto se manifestó como fallas aparentemente inexplicables en ARM64, donde async_chunk::inode se ve como no nulo en async_cow_submit, lo que hace que se llame a submission_compressed_extents y se produce una falla porque async_chunk::inode de repente se volvió NULL. El seguimiento de llamadas fue similar a: pc : submission_compressed_extents+0x38/0x3d0 lr : async_cow_submit+0x50/0xd0 sp : ffff800015d4bc20 Seguimiento de llamadas: submission_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 Solucione esto agregando las llamadas de barrera respectivas que garantizan que todos los accesos anteriores a la configuración de Los bits WORK_DONE_BIT se ordenan estrictamente antes de establecer la bandera. Al mismo tiempo, agregue una barrera de lectura después de la lectura de WORK_DONE_BIT en run_ordered_work que garantiza que todas las cargas posteriores se ordenarán estrictamente después de leer el bit. Esto, a su vez, garantiza que todos los accesos antes de WORK_DONE_BIT se ordenarán estrictamente antes de cualquier acceso que pueda ocurrir en ordered_func.

10 Apr 2024, 19:15

Type Values Removed Values Added
New CVE

Information

Published : 2024-04-10 19:15

Updated : 2025-04-30 16:34


NVD link : CVE-2021-47189

Mitre link : CVE-2021-47189

CVE.ORG link : CVE-2021-47189


JSON object : View

Products Affected

linux

  • linux_kernel