s390/crypto: Map EBUSY to EIO when key conversion fails repeatedly
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: Map EBUSY to EIO when key conversion fails repeatedly
When hardware persistently returns -EBUSY after exhausting retries, the error propagates to crypto_finalize_*_request(). The crypto API's completion wrapper treats -EBUSY as a queueing status and swallows it, preventing the completion callback from firing. This causes callers using crypto_wait_req() to block indefinitely.
Translate persistent -EBUSY to -EIO after retry exhaustion to ensure proper error propagation and callback invocation.
From the CVE record · Linux
The Linux kernel’s s390 crypto code can leave callers using crypto_wait_req() blocked indefinitely. This happens when hardware repeatedly returns -EBUSY during key conversion after retries are exhausted, and the crypto API treats the error as a queueing status instead of invoking the completion callback. The input does not specify an attacker path or access requirements.
Engineers running the Linux kernel with s390 crypto should check their installations; affected versions are not specified.