crypto: pcrypt - restore callback for non-parallel fallback
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 662f2f13e66d3883b9238b0b96b17886179e60e2 · < c4bd2f4c35b0e15b6040c2f7e7e7986780c066cf| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
crypto: pcrypt - restore callback for non-parallel fallback
pcrypt installs pcrypt_aead_done() on the child AEAD request before trying to submit it through padata. If padata_do_parallel() returns -EBUSY, pcrypt falls back to calling the child AEAD directly.
That fallback must not keep the padata completion callback. Otherwise an asynchronous completion runs pcrypt_aead_done() even though the request was never enrolled in padata.
Restore the original request callback and callback data before calling the child AEAD directly. This keeps the fallback path aligned with a direct AEAD request while leaving the parallel path unchanged.
From the CVE record · Linux
The Linux kernel’s pcrypt code can retain the wrong callback when padata_do_parallel() returns -EBUSY and the request falls back to direct AEAD processing. If the child AEAD completes asynchronously, it can run a padata completion callback even though the request was not enrolled in padata. The input does not specify an attacker path, authentication requirements, or user interaction.
Engineers running Linux kernels with pcrypt should check whether their kernel includes the fix; affected versions are not specified.