CVE-2024-56690: Linux kernel · crypto: pcrypt – Call crypto layer directly when padata_do_parallel() return -EBUSY
Affects Linux kernelSource GCVE Database
Not known to be exploited · CVSS 5.5 Medium · fixed in 5.4.0-1142.152~18.04.1 : update Linux kernel when convenient.
Data as of 29 Oct 2026, 22:35 UTC
- Patch
- Available – fixed in 5.4.0-1142.152~18.04.1, 5.4.0-1147.154~18.04.1, 5.4.0-1145.154~18.04.1 +82
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 28 Dec 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Patches and advisories
- ubuntu.com/security/notices/USN-7276-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7277-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7310-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7387-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7388-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7389-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7390-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7387-2 (opens in a new tab)
- ubuntu.com/security/notices/USN-7387-3 (opens in a new tab)
- ubuntu.com/security/notices/USN-7391-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7392-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7393-1 (opens in a new tab)
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Ubuntu 24.04 LTSlinuxpkg:deb/ubuntu/linux?arch=source&distro=nobleOther threats | Affected
| Fixed in
|
Ubuntu 24.04 LTSlinux-awspkg:deb/ubuntu/linux-aws?arch=source&distro=nobleOther threats | Affected
| Fixed in
|
Ubuntu 24.04 LTSlinux-azurepkg:deb/ubuntu/linux-azure?arch=source&distro=nobleOther threats | Affected
| Fixed in
|
Ubuntu 24.04 LTSlinux-azure-6.11pkg:deb/ubuntu/linux-azure-6.11?arch=source&distro=nobleOther threats | Affected
| Fixed in
|
Ubuntu 24.04 LTSlinux-azure-nvidiapkg:deb/ubuntu/linux-azure-nvidia?arch=source&distro=nobleOther threats | Affected
| Fixed in
|
Ubuntu 24.04 LTSlinux-gcppkg:deb/ubuntu/linux-gcp?arch=source&distro=nobleOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
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.
References
- ubuntu.com/security/CVE-2024-56690 (opens in a new tab)
- cve.org/CVERecord?id=CVE-2024-56690 (opens in a new tab)
- git.kernel.org/linus/662f2f13e66d3883b9238b0b96b17886179e60e2 (opens in a new tab)
- git.kernel.org/stable/c/5edae7a9a35606017ee6e05911c290acee9fee5a (opens in a new tab)
- git.kernel.org/stable/c/662f2f13e66d3883b9238b0b96b17886179e60e2 (opens in a new tab)
- git.kernel.org/stable/c/7ddab756f2de5b7b43c122ebebdf37f400fb2b6f (opens in a new tab)
- git.kernel.org/stable/c/92834692a539b5b7f409e467a14667d64713b732 (opens in a new tab)
- git.kernel.org/stable/c/96001f52ae8c70e2c736d3e1e5dc53d5b521e5ca (opens in a new tab)
- git.kernel.org/stable/c/a8e0074ffb38c9a5964a221bb998034d016c93a2 (opens in a new tab)
- git.kernel.org/stable/c/a92ccd3618e42333ac6f150ecdac14dca298bc7a (opens in a new tab)
- git.kernel.org/stable/c/dd8bf8eb5beba1e7c3b11a9a5a58ccbf345a69e6 (opens in a new tab)
- git.kernel.org/stable/c/fca8aed12218f96b38e374ff264d78ea1fbd23cc (opens in a new tab)
- ubuntu.com/security/notices/USN-7276-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7277-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7310-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7387-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7388-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7389-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7390-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7387-2 (opens in a new tab)