نسخههای متأثر
- نسخههای متأثر
- نامشخص
- نسخهٔ اصلاحشده
- اعلام نشده
بهرهبرداری
شرح آسیبپذیری
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.
A flaw was found in the Linux kernel's s390 cryptographic drivers. When handling asynchronous cryptographic operations, certain request callbacks incorrectly propagate error codes back to the crypto engine after already completing a request. This causes the crypto engine to mistakenly perform a second completion on the same request. A local user submitting cryptographic requests that encounter errors could trigger this condition, potentially leading to a kernel crash and a Denial of Service (DoS).

