s390/crypto: Fix handling of EBUSY in PHMAC when req is pushed to crypto engine
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 203702f0013f9b7324e8c5facb6cd6e9c0942b13, Kernel 330148371401de474b656eaf521861f12ec1a1ce and Kernel bcd7f1f1e2f2882ad206f72425255be105178151.
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.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | =6.17, >=cbbc675506cc4cd93e6f895e7c1f693156f9a95c <203702f0013f9b7324e8c5facb6cd6e9c0942b13, >=cbbc675506cc4cd93e6f895e7c1f693156f9a95c <330148371401de474b656eaf521861f12ec1a1ce, >=cbbc675506cc4cd93e6f895e7c1f693156f9a95c <bcd7f1f1e2f2882ad206f72425255be105178151 | 203702f0013f9b7324e8c5facb6cd6e9c0942b13, 330148371401de474b656eaf521861f12ec1a1ce, bcd7f1f1e2f2882ad206f72425255be105178151 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket