s390/crypto: Fix handling of EBUSY in PHMAC when req is pushed to crypto engine
- 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 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.
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
From cbbc675506cc4cd93e6f895e7c1f693156f9a95c · fixed in 203702f0013f9b7324e8c5facb6cd6e9c0942b13; From cbbc675506cc4cd93e6f895e7c1f693156f9a95c · fixed in bcd7f1f1e2f2882ad206f72425255be105178151; From cbbc675506cc4cd93e6f895e7c1f693156f9a95c · fixed in 330148371401de474b656eaf521861f12ec1a1ce
- Linux Linux
6.17
- KernelLinux
From 6.17.0 · fixed in 6.18.53; From 6.19.0 · fixed in 7.2.7