CVE-2026-97591: Linux kernel · s390/crypto: Fix handling of EBUSY in PHMAC when req is pushed to crypto engine
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in bcd7f1f1e2f2882ad206f72425255be105178151 : update Linux kernel when convenient.
Data as of 26 Oct 2026, 14:05 UTC
Rated by Threat Radar · CVSS not yet scored by NVD
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 9% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in bcd7f1f1e2f2882ad206f72425255be105178151, 330148371401de474b656eaf521861f12ec1a1ce, 203702f0013f9b7324e8c5facb6cd6e9c0942b13
Exploitation evidence
Disclosed: evidence found.
CVE published 25 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade Linux kernel to bcd7f1f1e2f2882ad206f72425255be105178151, 330148371401de474b656eaf521861f12ec1a1ce or 203702f0013f9b7324e8c5facb6cd6e9c0942b13.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in– |
AI-suggested
A patch is available and has been applied in the Linux kernel. The vendor manages remediation for this cloud-hosted service. Users should update to the fixed version to address this issue.
Description
A vulnerability in the Linux kernel's s390 crypto subsystem related to improper handling of the EBUSY return code in PHMAC when requests are pushed to the crypto engine has been fixed. The flaw involved missing correct handling of EBUSY as a successful transfer indication in the function crypto_transfer_hash_request_to_engine().