In the Linux kernel, the following vulnerability has been resolved: s390/crypto: Fix wrong return…

Why it is Yellow

• CVSS 7.0 high
• On your watchlist: linux kernel

References

• https://git.kernel.org/stable/c/5480291aa848e19e61175abfd457933516db70c6
• https://git.kernel.org/stable/c/972e0d9b7d1d112240ccde1f1be85bf9ffaa1720
• https://git.kernel.org/stable/c/ac1481320110b803ab9b79ab4d2ca11a74fc05f2

Original description

In the Linux kernel, the following vulnerability has been resolved: s390/crypto: Fix wrong return code to engine in asynch callbacks When crypto_finalize_hash_request() or crypto_finalize_skcipher_request() explicitly completes a request, the do_one_request callback must return 0 to indicate successful handling. Returning a negative error code causes the crypto engine to assume the driver failed to take ownership and triggers a second completion via crypto_request_complete(), resulting in a double completion. This pattern occurs in paes_s390.c 4 times and once in phmac_s390.c. Fixed in phmac_do_one_request() and all four paes do_one_request callbacks (ecb, cbc, ctr, xts) by returning 0 after explicit finalization instead of propagating the error code.