s390/crypto: Fix wrong return code to engine in asynch callbacks
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 6.18.53, 7.2.7
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
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.
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
From 6cd87cb5ef6ca50ae17c371482ceaab1d635e232 · fixed in 972e0d9b7d1d112240ccde1f1be85bf9ffaa1720; From 6cd87cb5ef6ca50ae17c371482ceaab1d635e232 · fixed in 5480291aa848e19e61175abfd457933516db70c6; From 6cd87cb5ef6ca50ae17c371482ceaab1d635e232 · fixed in ac1481320110b803ab9b79ab4d2ca11a74fc05f2
- Linux Linux
6.16
- KernelLinux
From 6.16.0 · fixed in 6.18.53; From 6.19.0 · fixed in 7.2.7