CVE-2021-47185

In the Linux kernel, the following vulnerability has been resolved: tty: tty_buffer: Fix the softlockup issue in flush_to_ldisc When running ltp testcase(ltp/testcases/kernel/pty/pty04.c) with arm64, there is a soft lockup, which look like this one: Workqueue: events_unbound flush_to_ldisc Call trace: dump_backtrace+0x0/0x1ec show_stack+0x24/0x30 dump_stack+0xd0/0x128 panic+0x15c/0x374 watchdog_timer_fn+0x2b8/0x304 __run_hrtimer+0x88/0x2c0 __hrtimer_run_queues+0xa4/0x120 hrtimer_interrupt+0xfc/0x270 arch_timer_handler_phys+0x40/0x50 handle_percpu_devid_irq+0x94/0x220 __handle_domain_irq+0x88/0xf0 gic_handle_irq+0x84/0xfc el1_irq+0xc8/0x180 slip_unesc+0x80/0x214 [slip] tty_ldisc_receive_buf+0x64/0x80 tty_port_default_receive_buf+0x50/0x90 flush_to_ldisc+0xbc/0x110 process_one_work+0x1d4/0x4b0 worker_thread+0x180/0x430 kthread+0x11c/0x120 In the testcase pty04, The first process call the write syscall to send data to the pty master. At the same time, the workqueue will do the flush_to_ldisc to pop data in a loop until there is no more data left. When the sender and workqueue running in different core, the sender sends data fastly in full time which will result in workqueue doing work in loop for a long time and occuring softlockup in flush_to_ldisc with kernel configured without preempt. So I add need_resched check and cond_resched in the flush_to_ldisc loop to avoid it.
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:*:*:*:*:*:*:*:*

History

21 Mar 2025, 14:59

Type Values Removed Values Added
First Time Linux linux Kernel
Linux
CWE CWE-667
CPE cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
References () https://git.kernel.org/stable/c/0380f643f3a7a61b0845cdc738959c2ad5735d61 - () https://git.kernel.org/stable/c/0380f643f3a7a61b0845cdc738959c2ad5735d61 - Patch
References () https://git.kernel.org/stable/c/3968ddcf05fb4b9409cd1859feb06a5b0550a1c1 - () https://git.kernel.org/stable/c/3968ddcf05fb4b9409cd1859feb06a5b0550a1c1 - Patch
References () https://git.kernel.org/stable/c/4c1623651a0936ee197859824cdae6ebbd04d3ed - () https://git.kernel.org/stable/c/4c1623651a0936ee197859824cdae6ebbd04d3ed - Patch
References () https://git.kernel.org/stable/c/4f300f47dbcf9c3d4b2ea76c8554c8f360400725 - () https://git.kernel.org/stable/c/4f300f47dbcf9c3d4b2ea76c8554c8f360400725 - Patch
References () https://git.kernel.org/stable/c/5c34486f04700f1ba04907231dce0cc2705c2d7d - () https://git.kernel.org/stable/c/5c34486f04700f1ba04907231dce0cc2705c2d7d - Patch
References () https://git.kernel.org/stable/c/77e9fed33056f2a88eba9dd4d2d5412f0c7d1f41 - () https://git.kernel.org/stable/c/77e9fed33056f2a88eba9dd4d2d5412f0c7d1f41 - Patch
References () https://git.kernel.org/stable/c/b1ffc16ec05ae40d82b6e373322d62e9d6b54fbc - () https://git.kernel.org/stable/c/b1ffc16ec05ae40d82b6e373322d62e9d6b54fbc - Patch
References () https://git.kernel.org/stable/c/d491c84df5c469dd9621863b6a770b3428137063 - () https://git.kernel.org/stable/c/d491c84df5c469dd9621863b6a770b3428137063 - Patch

21 Nov 2024, 06:35

Type Values Removed Values Added
References () https://git.kernel.org/stable/c/0380f643f3a7a61b0845cdc738959c2ad5735d61 - () https://git.kernel.org/stable/c/0380f643f3a7a61b0845cdc738959c2ad5735d61 -
References () https://git.kernel.org/stable/c/3968ddcf05fb4b9409cd1859feb06a5b0550a1c1 - () https://git.kernel.org/stable/c/3968ddcf05fb4b9409cd1859feb06a5b0550a1c1 -
References () https://git.kernel.org/stable/c/4c1623651a0936ee197859824cdae6ebbd04d3ed - () https://git.kernel.org/stable/c/4c1623651a0936ee197859824cdae6ebbd04d3ed -
References () https://git.kernel.org/stable/c/4f300f47dbcf9c3d4b2ea76c8554c8f360400725 - () https://git.kernel.org/stable/c/4f300f47dbcf9c3d4b2ea76c8554c8f360400725 -
References () https://git.kernel.org/stable/c/5c34486f04700f1ba04907231dce0cc2705c2d7d - () https://git.kernel.org/stable/c/5c34486f04700f1ba04907231dce0cc2705c2d7d -
References () https://git.kernel.org/stable/c/77e9fed33056f2a88eba9dd4d2d5412f0c7d1f41 - () https://git.kernel.org/stable/c/77e9fed33056f2a88eba9dd4d2d5412f0c7d1f41 -
References () https://git.kernel.org/stable/c/b1ffc16ec05ae40d82b6e373322d62e9d6b54fbc - () https://git.kernel.org/stable/c/b1ffc16ec05ae40d82b6e373322d62e9d6b54fbc -
References () https://git.kernel.org/stable/c/d491c84df5c469dd9621863b6a770b3428137063 - () https://git.kernel.org/stable/c/d491c84df5c469dd9621863b6a770b3428137063 -

01 Nov 2024, 15:35

Type Values Removed Values Added
CVSS v2 : unknown
v3 : unknown
v2 : unknown
v3 : 4.4
Summary
  • (es) En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: tty: tty_buffer: soluciona el problema de bloqueo suave en flush_to_ldisc Al ejecutar ltp testcase(ltp/testcases/kernel/pty/pty04.c) con arm64, hay un bloqueo suave, que se parece a este: Workqueue: events_unbound flush_to_ldisc Rastreo de llamadas: dump_backtrace+0x0/0x1ec show_stack+0x24/0x30 dump_stack+0xd0/0x128 panic+0x15c/0x374 watchdog_timer_fn+0x2b8/0x304 __run_hrtimer+0x88/0x2c0 __hrtimer_run_queues+0xa4/0x120 hrtimer_interrupt+0xfc/0x270 arch_timer_handler_phys+0x40/0x50 handle_percpu_devid_irq+0x94/0x220 __handle_domain_irq+0x88/0xf0 gic_handle_irq+0x84/0xfc el1_irq+0xc8/0x180 slip_unesc+0x80/0x214 [slip] tty_ldisc_receive_buf+0x64/0x80 tty_port_default_receive_buf+0x50/0x90 flush_to_ldisc+0xbc/0x110 process_one_work+0x1d4/0x4b0 worker_thread+0x180/0x430 kthread+0x11c/0x120 En el caso de prueba pty04, el primer proceso llama a la escritura Llamada al sistema para enviar datos al maestro pty. Al mismo tiempo, la cola de trabajo ejecutará el comando flush_to_ldisc para extraer los datos en un bucle hasta que no queden más datos. Cuando el remitente y la cola de trabajo se ejecutan en núcleos diferentes, el remitente envía datos rápidamente en tiempo completo, lo que hará que la cola de trabajo realice el trabajo en bucle durante mucho tiempo y se produzca un bloqueo suave en flush_to_ldisc con el núcleo configurado sin interrupción. Por lo tanto, agrego la comprobación need_resched y cond_resched en el bucle flush_to_ldisc para evitarlo.

10 Apr 2024, 19:49

Type Values Removed Values Added
New CVE

Information

Published : 2024-04-10 19:15

Updated : 2025-03-21 14:59


NVD link : CVE-2021-47185

Mitre link : CVE-2021-47185

CVE.ORG link : CVE-2021-47185


JSON object : View

Products Affected

linux

  • linux_kernel
CWE
CWE-667

Improper Locking