Vulnerability · Published May 21, 2024 · Assigned by Linux

CVE-2023-52813crypto: pcrypt - Fix hungtask for PADATA_RESET

Medium 5.5

In plain English

A medium-severity security flaw in Linux from Linux. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 0.3% (higher than 21% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.

Severity (CVSS NVD)5.5Medium
Exploit odds (30 days)0.3%top 78.8% of all CVEs
Exploited in the wildNo reportsCISA SSVC: none
Attack toolingNoneno public tooling known

Official description

In the Linux kernel, the following vulnerability has been resolved: crypto: pcrypt - Fix hungtask for PADATA_RESET We found a hungtask bug in test_aead_vec_cfg as follows: INFO: task cryptomgr_test:391009 blocked for more than 120 seconds. "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" 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 For padata_do_parallel, when the return err is 0 or -EBUSY, it will call wait_for_completion(&wait->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->flags is PADATA_RESET, the return err is -EBUSY for padata_do_parallel, and it won't call aead_request_complete(). Therefore, test_aead_vec_cfg will hung at wait_for_completion(&wait->completion), which will cause hungtask. The problem comes as following: (padata_do_parallel) | rcu_read_lock_bh(); | err = -EINVAL; | (padata_replace) | pinst->flags |= PADATA_RESET; err = -EBUSY | if (pinst->flags & PADATA_RESET) | rcu_read_unlock_bh() | return err In order to resolve the problem, we replace the return err -EBUSY with -EAGAIN, which means parallel_data is changing, and the caller should call it again. v3: remove retry and just change the return err. v2: introduce padata_try_do_parallel() in pcrypt_aead_encrypt and pcrypt_aead_decrypt to solve the hungtask.

Affected packages & fixed versions

EcosystemPackageFixed inAdvisory
AlmaLinux:8bpftool4.18.0-553.8.1.el8_10ALSA-2024:4211
AlmaLinux:8kernel4.18.0-553.8.1.el8_10ALSA-2024:4211
AlmaLinux:8kernel-abi-stablelists4.18.0-553.8.1.el8_10ALSA-2024:4211
AlmaLinux:8kernel-core4.18.0-553.8.1.el8_10ALSA-2024:4211
AlmaLinux:8kernel-cross-headers4.18.0-553.8.1.el8_10ALSA-2024:4211
AlmaLinux:8kernel-debug4.18.0-553.8.1.el8_10ALSA-2024:4211
AlmaLinux:8kernel-debug-core4.18.0-553.8.1.el8_10ALSA-2024:4211
AlmaLinux:8kernel-debug-devel4.18.0-553.8.1.el8_10ALSA-2024:4211
AlmaLinux:8kernel-debug-modules4.18.0-553.8.1.el8_10ALSA-2024:4211
AlmaLinux:8kernel-debug-modules-extra4.18.0-553.8.1.el8_10ALSA-2024:4211
AlmaLinux:8kernel-devel4.18.0-553.8.1.el8_10ALSA-2024:4211
AlmaLinux:8kernel-doc4.18.0-553.8.1.el8_10ALSA-2024:4211
AlmaLinux:8kernel-headers4.18.0-553.8.1.el8_10ALSA-2024:4211
AlmaLinux:8kernel-modules4.18.0-553.8.1.el8_10ALSA-2024:4211
AlmaLinux:8kernel-modules-extra4.18.0-553.8.1.el8_10ALSA-2024:4211
AlmaLinux:8kernel-rt4.18.0-553.8.1.rt7.349.el8_10ALSA-2024:4352
AlmaLinux:8kernel-rt-core4.18.0-553.8.1.rt7.349.el8_10ALSA-2024:4352
AlmaLinux:8kernel-rt-debug4.18.0-553.8.1.rt7.349.el8_10ALSA-2024:4352
AlmaLinux:8kernel-rt-debug-core4.18.0-553.8.1.rt7.349.el8_10ALSA-2024:4352
AlmaLinux:8kernel-rt-debug-devel4.18.0-553.8.1.rt7.349.el8_10ALSA-2024:4352
AlmaLinux:8kernel-rt-debug-kvm4.18.0-553.8.1.rt7.349.el8_10ALSA-2024:4352
AlmaLinux:8kernel-rt-debug-modules4.18.0-553.8.1.rt7.349.el8_10ALSA-2024:4352
AlmaLinux:8kernel-rt-debug-modules-extra4.18.0-553.8.1.rt7.349.el8_10ALSA-2024:4352
AlmaLinux:8kernel-rt-devel4.18.0-553.8.1.rt7.349.el8_10ALSA-2024:4352
AlmaLinux:8kernel-rt-kvm4.18.0-553.8.1.rt7.349.el8_10ALSA-2024:4352
AlmaLinux:8kernel-rt-modules4.18.0-553.8.1.rt7.349.el8_10ALSA-2024:4352
AlmaLinux:8kernel-rt-modules-extra4.18.0-553.8.1.rt7.349.el8_10ALSA-2024:4352
AlmaLinux:8kernel-tools4.18.0-553.8.1.el8_10ALSA-2024:4211
AlmaLinux:8kernel-tools-libs4.18.0-553.8.1.el8_10ALSA-2024:4211
AlmaLinux:8kernel-tools-libs-devel4.18.0-553.8.1.el8_10ALSA-2024:4211
AlmaLinux:8kernel-zfcpdump4.18.0-553.8.1.el8_10ALSA-2024:4211
AlmaLinux:8kernel-zfcpdump-core4.18.0-553.8.1.el8_10ALSA-2024:4211
AlmaLinux:8kernel-zfcpdump-devel4.18.0-553.8.1.el8_10ALSA-2024:4211
AlmaLinux:8kernel-zfcpdump-modules4.18.0-553.8.1.el8_10ALSA-2024:4211
AlmaLinux:8kernel-zfcpdump-modules-extra4.18.0-553.8.1.el8_10ALSA-2024:4211
AlmaLinux:8perf4.18.0-553.8.1.el8_10ALSA-2024:4211
AlmaLinux:8python3-perf4.18.0-553.8.1.el8_10ALSA-2024:4211
Debian:12linux6.1.64-1DEBIAN-CVE-2023-52813
Debian:13linux6.6.8-1DEBIAN-CVE-2023-52813
Debian:14linux6.6.8-1DEBIAN-CVE-2023-52813
Rocky Linux:8kernel0:4.18.0-553.8.1.el8_10RLSA-2024:4211
Rocky Linux:8kernel-rt0:4.18.0-553.8.1.rt7.349.el8_10RLSA-2024:4352
Ubuntu:22.04:LTSlinux5.15.0-100.110UBUNTU-CVE-2023-52813
Ubuntu:22.04:LTSlinux-allwinner-5.19no fix listedUBUNTU-CVE-2023-52813
Ubuntu:22.04:LTSlinux-aws5.15.0-1056.61UBUNTU-CVE-2023-52813
Ubuntu:22.04:LTSlinux-aws-5.19no fix listedUBUNTU-CVE-2023-52813
Ubuntu:22.04:LTSlinux-aws-6.2no fix listedUBUNTU-CVE-2023-52813
Ubuntu:22.04:LTSlinux-aws-6.5no fix listedUBUNTU-CVE-2023-52813
Ubuntu:22.04:LTSlinux-azure5.15.0-1058.66UBUNTU-CVE-2023-52813
Ubuntu:22.04:LTSlinux-azure-5.19no fix listedUBUNTU-CVE-2023-52813
Ubuntu:22.04:LTSlinux-azure-6.2no fix listedUBUNTU-CVE-2023-52813
Ubuntu:22.04:LTSlinux-azure-6.5no fix listedUBUNTU-CVE-2023-52813
Ubuntu:22.04:LTSlinux-azure-fde5.15.0-1058.66.1UBUNTU-CVE-2023-52813
Ubuntu:22.04:LTSlinux-azure-fde-5.19no fix listedUBUNTU-CVE-2023-52813
Ubuntu:22.04:LTSlinux-azure-fde-6.2no fix listedUBUNTU-CVE-2023-52813
Ubuntu:22.04:LTSlinux-gcp5.15.0-1053.61UBUNTU-CVE-2023-52813
Ubuntu:22.04:LTSlinux-gcp-5.19no fix listedUBUNTU-CVE-2023-52813
Ubuntu:22.04:LTSlinux-gcp-6.2no fix listedUBUNTU-CVE-2023-52813
Ubuntu:22.04:LTSlinux-gcp-6.5no fix listedUBUNTU-CVE-2023-52813
Ubuntu:22.04:LTSlinux-gke5.15.0-1052.57UBUNTU-CVE-2023-52813
Ubuntu:22.04:LTSlinux-gkeop5.15.0-1038.44UBUNTU-CVE-2023-52813
Ubuntu:22.04:LTSlinux-hwe-5.19no fix listedUBUNTU-CVE-2023-52813
Ubuntu:22.04:LTSlinux-hwe-6.2no fix listedUBUNTU-CVE-2023-52813
Ubuntu:22.04:LTSlinux-hwe-6.5no fix listedUBUNTU-CVE-2023-52813
Ubuntu:22.04:LTSlinux-ibm5.15.0-1048.51UBUNTU-CVE-2023-52813
Ubuntu:22.04:LTSlinux-intel-iotg5.15.0-1050.56UBUNTU-CVE-2023-52813
Ubuntu:22.04:LTSlinux-kvm5.15.0-1052.57UBUNTU-CVE-2023-52813
Ubuntu:22.04:LTSlinux-lowlatency5.15.0-100.110UBUNTU-CVE-2023-52813
Ubuntu:22.04:LTSlinux-lowlatency-hwe-5.19no fix listedUBUNTU-CVE-2023-52813
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.2no fix listedUBUNTU-CVE-2023-52813
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.5no fix listedUBUNTU-CVE-2023-52813
Ubuntu:22.04:LTSlinux-nvidia5.15.0-1046.46UBUNTU-CVE-2023-52813
Ubuntu:22.04:LTSlinux-nvidia-6.2no fix listedUBUNTU-CVE-2023-52813
Ubuntu:22.04:LTSlinux-nvidia-6.56.5.0-1014.14UBUNTU-CVE-2023-52813
Ubuntu:22.04:LTSlinux-nvidia-tegra5.15.0-1025.25UBUNTU-CVE-2023-52813
Ubuntu:22.04:LTSlinux-nvidia-tegra-igx5.15.0-1012.12UBUNTU-CVE-2023-52813
Ubuntu:22.04:LTSlinux-oem-5.17no fix listedUBUNTU-CVE-2023-52813
Ubuntu:22.04:LTSlinux-oem-6.0no fix listedUBUNTU-CVE-2023-52813
Ubuntu:22.04:LTSlinux-oem-6.1no fix listedUBUNTU-CVE-2023-52813
Ubuntu:22.04:LTSlinux-oem-6.5no fix listedUBUNTU-CVE-2023-52813
Ubuntu:22.04:LTSlinux-oracle5.15.0-1053.59UBUNTU-CVE-2023-52813
Ubuntu:22.04:LTSlinux-oracle-6.5no fix listedUBUNTU-CVE-2023-52813
Ubuntu:22.04:LTSlinux-raspi5.15.0-1048.51UBUNTU-CVE-2023-52813
Ubuntu:24.04:LTSlinux-raspi-realtimeno fix listedUBUNTU-CVE-2023-52813
Ubuntu:22.04:LTSlinux-realtimeno fix listedUBUNTU-CVE-2023-52813
Ubuntu:22.04:LTSlinux-riscvno fix listedUBUNTU-CVE-2023-52813
Ubuntu:22.04:LTSlinux-riscv-5.19no fix listedUBUNTU-CVE-2023-52813
Ubuntu:22.04:LTSlinux-riscv-6.5no fix listedUBUNTU-CVE-2023-52813
Ubuntu:22.04:LTSlinux-starfive-5.19no fix listedUBUNTU-CVE-2023-52813
Ubuntu:22.04:LTSlinux-starfive-6.2no fix listedUBUNTU-CVE-2023-52813
Ubuntu:22.04:LTSlinux-starfive-6.5no fix listedUBUNTU-CVE-2023-52813
Ubuntu:22.04:LTSlinux-xilinx-zynqmp5.15.0-1030.34UBUNTU-CVE-2023-52813

Affected products (as reported)

VendorProductVersions
Linux Linux 16295bec6398a3eedc9377e1af6ff4c71b98c300 – before fb2d3a50a8f29a3c66682bb426144f40e32ab81816295bec6398a3eedc9377e1af6ff4c71b98c300 – before 039fec48e062504f14845124a1a25eb199b2ddc016295bec6398a3eedc9377e1af6ff4c71b98c300 – before c9c1334697301c10e6918d747ed38abfbc0c96e716295bec6398a3eedc9377e1af6ff4c71b98c300 – before e97bf4ada7dddacd184c3e196bd063b0dc71b41d16295bec6398a3eedc9377e1af6ff4c71b98c300 – before 546c1796ad1ed0d87dab3c4b5156d75819be231616295bec6398a3eedc9377e1af6ff4c71b98c300 – before c55fc098fd9d2dca475b82d00ffbcaf97879d77e16295bec6398a3eedc9377e1af6ff4c71b98c300 – before e134f3aba98e6c801a693f540912c2d493718ddf16295bec6398a3eedc9377e1af6ff4c71b98c300 – before 372636debe852913529b1716f44addd94fff2d28
Linux Linux 2.6.34

References