U.S. flag   An official website of the United States government
Dot gov

Official websites use .gov
A .gov website belongs to an official government organization in the United States.

Https

Secure .gov websites use HTTPS
A lock (Dot gov) or https:// means you've safely connected to the .gov website. Share sensitive information only on official, secure websites.

Vulnerability Change Records for CVE-2021-47377

Change History

CVE Translated by kernel.org 5/28/2024 3:15:08 PM

Action Type Old Value New Value
Removed Translation
Title: kernel de Linux
Description:  En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: xen/balloon: utiliza un subproceso del kernel en lugar de una cola de trabajo. Hoy en día, la expansión de Xen se realiza mediante trabajo retrasado en una cola de trabajo. Esto podría provocar que se informen bloqueos de la cola de trabajo en caso de que se aumenten grandes cantidades de memoria de una vez (aquí 16 GB): BUG: bloqueo de la cola de trabajo - pool cpus=6 node=0 flags=0x0 nice=0 bloqueado durante 64 segundos. Mostrando colas de trabajo ocupadas y grupos de trabajadores: eventos de cola de trabajo: flags=0x0 pwq 12: cpus=6 node=0 flags=0x0 nice=0 active=2/256 refcnt=3 en vuelo: 229:balloon_process pendiente: cache_reap workqueue events_freezable_power_: flags =0x84 pwq 12: cpus=6 nodo=0 banderas=0x0 agradable=0 activo=1/256 refcnt=2 pendiente: disk_events_workfn cola de trabajo mm_percpu_wq: banderas=0x8 pwq 12: cpus=6 nodo=0 banderas=0x0 agradable=0 activo =1/256 refcnt=2 pendiente: vmstat_update pool 12: cpus=6 nodo=0 banderas=0x0 agradable=0 colgado=64s trabajadores=3 inactivo: 2222 43 Esto se puede evitar fácilmente usando un subproceso del kernel dedicado para realizar la expansión trabajar.

								
						

CVE Modified by kernel.org 5/28/2024 3:15:08 PM

Action Type Old Value New Value
Changed Description
In the Linux kernel, the following vulnerability has been resolved:

xen/balloon: use a kernel thread instead a workqueue

Today the Xen ballooning is done via delayed work in a workqueue. This
might result in workqueue hangups being reported in case of large
amounts of memory are being ballooned in one go (here 16GB):

BUG: workqueue lockup - pool cpus=6 node=0 flags=0x0 nice=0 stuck for 64s!
Showing busy workqueues and worker pools:
workqueue events: flags=0x0
  pwq 12: cpus=6 node=0 flags=0x0 nice=0 active=2/256 refcnt=3
    in-flight: 229:balloon_process
    pending: cache_reap
workqueue events_freezable_power_: flags=0x84
  pwq 12: cpus=6 node=0 flags=0x0 nice=0 active=1/256 refcnt=2
    pending: disk_events_workfn
workqueue mm_percpu_wq: flags=0x8
  pwq 12: cpus=6 node=0 flags=0x0 nice=0 active=1/256 refcnt=2
    pending: vmstat_update
pool 12: cpus=6 node=0 flags=0x0 nice=0 hung=64s workers=3 idle: 2222 43

This can easily be avoided by using a dedicated kernel thread for doing
the ballooning work.
Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.
Removed Reference
kernel.org https://git.kernel.org/stable/c/29917bbb07c30be295dece245c7c21872e1a6fbb

								
						
Removed Reference
kernel.org https://git.kernel.org/stable/c/372d3e6ea1e115942fdfb4b25f7003d822d071be

								
						
Removed Reference
kernel.org https://git.kernel.org/stable/c/6bba79c6a073741b672b0bf86a1f03c0fe47f973

								
						
Removed Reference
kernel.org https://git.kernel.org/stable/c/8480ed9c2bbd56fc86524998e5f2e3e22f5038f6

								
						
Removed Reference
kernel.org https://git.kernel.org/stable/c/922fd5b6bb13ad31ff36e86e2eba2f26d8135272

								
						
Removed Reference
kernel.org https://git.kernel.org/stable/c/c5d5a43dd2b649a0a290bfed00fb76d1aff89be6

								
						

CVE Rejected by kernel.org 5/28/2024 3:15:08 PM

Action Type Old Value New Value