crypto: pcrypt - Call crypto layer directly when padata_do_parallel() return -EBUSY
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 372636debe852913529b1716f44addd94fff2d28 · < 5edae7a9a35606017ee6e05911c290acee9fee5a| No fix yet |
| Linux Linux |
|
|
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.
From the CVE record · Linux
Linux kernel pcrypt encryption and decryption can return -EAGAIN when a CPU goes online or offline, causing alg_test() to generate a warning. If panic_on_warn is set to 1, that warning can cause a kernel panic. The input does not specify an attacker path or authentication requirements.
Engineers running Linux kernels with the affected pcrypt behavior should check their builds; affected versions are not specified.