s390/crypto: Fix handling of EBUSY in PHMAC when req is pushed to crypto engine
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
6.18.537.2.77.3In 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.
From the CVE record · Linux
The Linux kernel’s s390 PHMAC code incorrectly handles EBUSY when transferring a hash request to the crypto engine, even though EBUSY can indicate a successful transfer. The input does not specify an attacker outcome or whether exploitation requires network access, local access, authentication, or user interaction.
Engineers running the Linux kernel with s390 PHMAC should check their installations; affected versions are not specified.