In the Linux kernel, the following vulnerability has been resolved: s390/crypto: Fix handling of EBUSY in PHMAC when req is pushed to crypto engine When a request is transferred to the engine via crypto_transfer_hash_request_to_engine() there are two return codes signaling a successful transfer: EINPROGRESS and EBUSY. However the correct handling of EBUSY was missing and has been added as a return code indicating a successful transfer to the crypto engine.
https://git.kernel.org/stable/c/bcd7f1f1e2f2882ad206f72425255be105178151
https://git.kernel.org/stable/c/330148371401de474b656eaf521861f12ec1a1ce
https://git.kernel.org/stable/c/203702f0013f9b7324e8c5facb6cd6e9c0942b13