https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Wed, 07 Oct 2026 14:58:53 +0000 https://cve.radiocsirt.org/vuln/cve-2023-52813 <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>crypto: pcrypt - Fix hungtask for PADATA_RESET</p> <p>We found a hungtask bug in test_aead_vec_cfg as follows:</p> <p>INFO: task cryptomgr_test:391009 blocked for more than 120 seconds. &#34;echo 0 &gt; /proc/sys/kernel/hung_task_timeout_secs&#34; disables this message. Call trace: __switch_to+0x98/0xe0 __schedule+0x6c4/0xf40 schedule+0xd8/0x1b4 schedule_timeout+0x474/0x560 wait_for_common+0x368/0x4e0 wait_for_completion+0x20/0x30 wait_for_completion+0x20/0x30 test_aead_vec_cfg+0xab4/0xd50 test_aead+0x144/0x1f0 alg_test_aead+0xd8/0x1e0 alg_test+0x634/0x890 cryptomgr_test+0x40/0x70 kthread+0x1e0/0x220 ret_from_fork+0x10/0x18 Kernel panic - not syncing: hung_task: blocked tasks</p> <p>For padata_do_parallel, when the return err is 0 or -EBUSY, it will call wait_for_completion(&amp;wait-&gt;completion) in test_aead_vec_cfg. In normal case, aead_request_complete() will be called in pcrypt_aead_serial and the return err is 0 for padata_do_parallel. But, when pinst-&gt;flags is PADATA_RESET, the return err is -EBUSY for padata_do_parallel, and it won&#39;t call aead_request_complete(). Therefore, test_aead_vec_cfg will hung at wait_for_completion(&amp;wait-&gt;completion), which will cause hungtask.</p> <p>The problem comes as following: (padata_do_parallel) | rcu_read_lock_bh(); | err = -EINVAL; | (padata_replace) | pinst-&gt;flags |= PADATA_RESET; err =…</p> <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>crypto: pcrypt - Fix hungtask for PADATA_RESET</p> <p>We found a hungtask bug in test_aead_vec_cfg as follows:</p> <p>INFO: task cryptomgr_test:391009 blocked for more than 120 seconds. &#34;echo 0 &gt; /proc/sys/kernel/hung_task_timeout_secs&#34; disables this message. Call trace: __switch_to+0x98/0xe0 __schedule+0x6c4/0xf40 schedule+0xd8/0x1b4 schedule_timeout+0x474/0x560 wait_for_common+0x368/0x4e0 wait_for_completion+0x20/0x30 wait_for_completion+0x20/0x30 test_aead_vec_cfg+0xab4/0xd50 test_aead+0x144/0x1f0 alg_test_aead+0xd8/0x1e0 alg_test+0x634/0x890 cryptomgr_test+0x40/0x70 kthread+0x1e0/0x220 ret_from_fork+0x10/0x18 Kernel panic - not syncing: hung_task: blocked tasks</p> <p>For padata_do_parallel, when the return err is 0 or -EBUSY, it will call wait_for_completion(&amp;wait-&gt;completion) in test_aead_vec_cfg. In normal case, aead_request_complete() will be called in pcrypt_aead_serial and the return err is 0 for padata_do_parallel. But, when pinst-&gt;flags is PADATA_RESET, the return err is -EBUSY for padata_do_parallel, and it won&#39;t call aead_request_complete(). Therefore, test_aead_vec_cfg will hung at wait_for_completion(&amp;wait-&gt;completion), which will cause hungtask.</p> <p>The problem comes as following: (padata_do_parallel) | rcu_read_lock_bh(); | err = -EINVAL; | (padata_replace) | pinst-&gt;flags |= PADATA_RESET; err =…</p> https://cve.radiocsirt.org/vuln/cve-2023-52813