# CVE-2024-56690: crypto: pcrypt - Call crypto layer directly when padata_do_parallel() return -EBUSY > A kernel bug in pcrypt causes a panic when CPU hotplug events occur if panic_on_warn is enabled, leading to denial of service. - **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H`) - **Exploited in the wild:** Not known - **Login needed:** Any signed-in user - **Attackable:** Local or same network only - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 28 Dec 2024 - **Updated:** 23 May 2026 - **Also known as:** BELL-CVE-2024-56690, DEBIAN-CVE-2024-56690, GHSA-4w8p-fpvp-22x8, RHSA-2025:21563, UBUNTU-CVE-2024-56690 ## What is CVE-2024-56690? CVE-2024-56690 is a medium-severity denial of service vulnerability in Linux kernel, published on 28 Dec 2024. It can only be exploited from the same machine or local network, with no action from the victim. ### Official description In the Linux kernel, the following vulnerability has been resolved: crypto: pcrypt - Call crypto layer directly when padata_do_parallel() return -EBUSY Since commit 8f4f68e788c3 ("crypto: pcrypt - Fix hungtask for PADATA_RESET"), the pcrypt encryption and decryption operations return -EAGAIN when the CPU goes online or offline. In alg_test(), a WARN is generated when pcrypt_aead_decrypt() or pcrypt_aead_encrypt() returns -EAGAIN, the unnecessary panic will occur when panic_on_warn set 1. Fix this issue by calling crypto layer directly without parallelization in that case. ## Which versions are affected by CVE-2024-56690? It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `kernel-64k-debug-debuginfo` | Red Hat:rhel_eus:9.6::appstream | All versions | 0:5.14.0-570.64.1.el9_6 | | `kernel-64k-debug-devel` | Red Hat:rhel_eus:9.6::appstream | All versions | 0:5.14.0-570.64.1.el9_6 | | `kernel-64k-debug-devel-matched` | Red Hat:rhel_eus:9.6::appstream | All versions | 0:5.14.0-570.64.1.el9_6 | | `kernel-64k-debuginfo` | Red Hat:rhel_eus:9.6::appstream | All versions | 0:5.14.0-570.64.1.el9_6 | | `kernel-64k-devel` | Red Hat:rhel_eus:9.6::appstream | All versions | 0:5.14.0-570.64.1.el9_6 | | `kernel-64k-devel-matched` | Red Hat:rhel_eus:9.6::appstream | All versions | 0:5.14.0-570.64.1.el9_6 | | `kernel-debug-debuginfo` | Red Hat:rhel_eus:9.6::appstream | All versions | 0:5.14.0-570.64.1.el9_6 | | `kernel-debug-devel` | Red Hat:rhel_eus:9.6::appstream | All versions | 0:5.14.0-570.64.1.el9_6 | | `kernel-debug-devel-matched` | Red Hat:rhel_eus:9.6::appstream | All versions | 0:5.14.0-570.64.1.el9_6 | | `kernel-debuginfo` | Red Hat:rhel_eus:9.6::appstream | All versions | 0:5.14.0-570.64.1.el9_6 | | `kernel-debuginfo-common-aarch64` | Red Hat:rhel_eus:9.6::appstream | All versions | 0:5.14.0-570.64.1.el9_6 | | `kernel-debuginfo-common-ppc64le` | Red Hat:rhel_eus:9.6::appstream | All versions | 0:5.14.0-570.64.1.el9_6 | | `kernel-debuginfo-common-s390x` | Red Hat:rhel_eus:9.6::appstream | All versions | 0:5.14.0-570.64.1.el9_6 | | `kernel-debuginfo-common-x86_64` | Red Hat:rhel_eus:9.6::appstream | All versions | 0:5.14.0-570.64.1.el9_6 | | `kernel-devel` | Red Hat:rhel_eus:9.6::appstream | All versions | 0:5.14.0-570.64.1.el9_6 | | `kernel-devel-matched` | Red Hat:rhel_eus:9.6::appstream | All versions | 0:5.14.0-570.64.1.el9_6 | | `kernel-doc` | Red Hat:rhel_eus:9.6::appstream | All versions | 0:5.14.0-570.64.1.el9_6 | | `kernel-rt-64k-debug-debuginfo` | Red Hat:rhel_eus:9.6::appstream | All versions | 0:5.14.0-570.64.1.el9_6 | | `kernel-rt-64k-debuginfo` | Red Hat:rhel_eus:9.6::appstream | All versions | 0:5.14.0-570.64.1.el9_6 | | `kernel-rt-debug-debuginfo` | Red Hat:rhel_eus:9.6::appstream | All versions | 0:5.14.0-570.64.1.el9_6 | | `kernel-rt-debuginfo` | Red Hat:rhel_eus:9.6::appstream | All versions | 0:5.14.0-570.64.1.el9_6 | | `kernel-tools-debuginfo` | Red Hat:rhel_eus:9.6::appstream | All versions | 0:5.14.0-570.64.1.el9_6 | | `kernel-zfcpdump-debuginfo` | Red Hat:rhel_eus:9.6::appstream | All versions | 0:5.14.0-570.64.1.el9_6 | | `kernel-zfcpdump-devel` | Red Hat:rhel_eus:9.6::appstream | All versions | 0:5.14.0-570.64.1.el9_6 | | `kernel-zfcpdump-devel-matched` | Red Hat:rhel_eus:9.6::appstream | All versions | 0:5.14.0-570.64.1.el9_6 | | `libperf-debuginfo` | Red Hat:rhel_eus:9.6::appstream | All versions | 0:5.14.0-570.64.1.el9_6 | | `perf` | Red Hat:rhel_eus:9.6::appstream | All versions | 0:5.14.0-570.64.1.el9_6 | | `perf-debuginfo` | Red Hat:rhel_eus:9.6::appstream | All versions | 0:5.14.0-570.64.1.el9_6 | | `python3-perf` | Red Hat:rhel_eus:9.6::appstream | All versions | 0:5.14.0-570.64.1.el9_6 | | `python3-perf-debuginfo` | Red Hat:rhel_eus:9.6::appstream | All versions | 0:5.14.0-570.64.1.el9_6 | | `rtla` | Red Hat:rhel_eus:9.6::appstream | All versions | 0:5.14.0-570.64.1.el9_6 | | `rv` | Red Hat:rhel_eus:9.6::appstream | All versions | 0:5.14.0-570.64.1.el9_6 | | `kernel` | Red Hat:rhel_eus:9.6::baseos | All versions | 0:5.14.0-570.64.1.el9_6 | | `kernel-64k` | Red Hat:rhel_eus:9.6::baseos | All versions | 0:5.14.0-570.64.1.el9_6 | | `kernel-64k-core` | Red Hat:rhel_eus:9.6::baseos | All versions | 0:5.14.0-570.64.1.el9_6 | | `kernel-64k-debug` | Red Hat:rhel_eus:9.6::baseos | All versions | 0:5.14.0-570.64.1.el9_6 | | `kernel-64k-debug-core` | Red Hat:rhel_eus:9.6::baseos | All versions | 0:5.14.0-570.64.1.el9_6 | | `kernel-64k-debug-debuginfo` | Red Hat:rhel_eus:9.6::baseos | All versions | 0:5.14.0-570.64.1.el9_6 | | `kernel-64k-debug-modules` | Red Hat:rhel_eus:9.6::baseos | All versions | 0:5.14.0-570.64.1.el9_6 | | `kernel-64k-debug-modules-core` | Red Hat:rhel_eus:9.6::baseos | All versions | 0:5.14.0-570.64.1.el9_6 | Products: Linux kernel. ## How do I fix CVE-2024-56690? Apply the vendor's patch. ## Is CVE-2024-56690 being exploited? There is no known exploitation of CVE-2024-56690 in the wild and no public exploit code. ## Other vulnerabilities in Linux kernel - [CVE-2026-53266](https://insights.sbomify.com/CVE-2026-53266/): Linux Kernel Out-of-Bounds Write (high 8.8, exploited in the wild) - [CVE-2013-6282](https://insights.sbomify.com/CVE-2013-6282/): Linux Kernel Improper Input Validation (high 8.8, exploited in the wild) - [CVE-2022-0185](https://insights.sbomify.com/CVE-2022-0185/): Linux Kernel Heap-Based Buffer Overflow (high 8.4, exploited in the wild) - [CVE-2013-2094](https://insights.sbomify.com/CVE-2013-2094/): Linux Kernel Privilege Escalation (high 8.4, exploited in the wild) - [CVE-2026-53362](https://insights.sbomify.com/CVE-2026-53362/): Linux Kernel Unspecified (high 7.8, exploited in the wild) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2024-56690 and fix it if it is affected. What it is: CVE-2024-56690 is a medium-severity denial of service vulnerability in Linux kernel, published on 28 Dec 2024. It can only be exploited from the same machine or local network, with no action from the victim. Exploitation: There is no known exploitation of CVE-2024-56690 in the wild and no public exploit code. Affected product: Linux kernel. No package-level version data is available, so check the vendor advisory linked from the reference page. Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2024-56690/ (Markdown: https://insights.sbomify.com/CVE-2024-56690/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2024-56690 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-56690 - OSV: https://osv.dev/vulnerability/CVE-2024-56690 --- From sbomify Insights: https://insights.sbomify.com/CVE-2024-56690/ Summaries are generated and may contain mistakes; the official description above is the record.