CVE-2024-56690: crypto: pcrypt - Call crypto layer directly when padata_do_parallel() return -EBUSY
In the Linux kernel, the following vulnerability has been resolved:
crypto: pcrypt - Call crypto layer directly when padatadoparallel() return -EBUSY
Since commit 8f4f68e788c3 ("crypto: pcrypt - Fix hungtask for PADATARESET"), the pcrypt encryption and decryption operations return -EAGAIN when the CPU goes online or offline. In algtest(), a WARN is generated when pcryptaeaddecrypt() or pcryptaeadencrypt() returns -EAGAIN, the unnecessary panic will occur when paniconwarn set 1. Fix this issue by calling crypto layer directly without parallelization in that case.
Other sources
This CVE was automatically created from a reference found in an email or other text. If you are reading this, then this CVE entry is probably erroneous, since this text should be replaced by the official CVE description automatically.
— Launchpad
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
debian/linuxto a version that resolves this vulnerability.Fixed in 5.10.234-1Fixed in 6.1.129-1Fixed in 6.1.135-1Fixed in 6.12.25-1Fixed in 6.12.27-1 - Upgrade
Upgrade
debian/linux-6.1to a version that resolves this vulnerability.Fixed in 6.1.129-1~deb11u1
Event History
Frequently Asked Questions
What is the severity of CVE-2024-56690?
CVE-2024-56690 has a moderate severity rating due to its impact on the Linux kernel's crypto operations.
How do I fix CVE-2024-56690?
To fix CVE-2024-56690, update the Linux kernel to the latest version that includes the patch.
What systems are affected by CVE-2024-56690?
CVE-2024-56690 affects all versions of the Linux kernel prior to the patch release addressing this vulnerability.
What are the potential consequences of CVE-2024-56690?
Exploitation of CVE-2024-56690 could lead to denial of service in encryption and decryption operations.
Is there a workaround for CVE-2024-56690?
Currently, there are no known effective workarounds for CVE-2024-56690 other than applying the kernel update.