Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2026-97591 Overview
CVE-2026-97591 is a vulnerability in the Linux kernel affecting the s390 architecture's PHMAC (Protected HMAC) crypto driver. The flaw involves improper handling of the EBUSY return code when a hash request is transferred to the crypto engine via crypto_transfer_hash_request_to_engine(). The function returns one of two success codes, EINPROGRESS or EBUSY, but only EINPROGRESS was treated as successful. This caused valid, queued requests to be incorrectly processed as failures within the s390 crypto subsystem.
Critical Impact
Mishandling of the EBUSY success code in the PHMAC driver can lead to incorrect request completion handling on IBM Z (s390) systems, potentially causing cryptographic operation errors or kernel instability.
Affected Products
- Linux kernel (upstream, s390 architecture)
- Kernel builds using the s390/crypto PHMAC driver
- Stable kernel branches referenced by commits 203702f, 3301483, and bcd7f1f
Discovery Timeline
- 2026-09-25 - CVE-2026-97591 published to NVD
- 2026-09-25 - Last updated in NVD database
Technical Details for CVE-2026-97591
Vulnerability Analysis
The vulnerability resides in the s390 PHMAC (Protected HMAC) crypto driver in the Linux kernel. When the driver submits a hash request to the crypto engine using crypto_transfer_hash_request_to_engine(), the kernel API signals successful transfer with either EINPROGRESS or EBUSY. The EBUSY code indicates the request was accepted and queued because the engine is currently processing another operation. The original PHMAC implementation only treated EINPROGRESS as a successful transfer and failed to account for EBUSY, causing valid queued operations to be mishandled.
Root Cause
The root cause is incomplete return-code validation in the PHMAC driver's submission path. The driver assumed a single success value from crypto_transfer_hash_request_to_engine() rather than both documented success values. This resulted in the error branch being taken for correctly queued requests, leading to inconsistent state tracking between the driver and the crypto engine.
Attack Vector
The issue is a kernel-side correctness defect rather than a directly exploitable remote vector. It is triggered during normal cryptographic workloads on IBM Z (s390) hardware when the crypto engine is sufficiently busy to return EBUSY. The vulnerability does not have an assigned CWE or CVSS vector at publication. The upstream fix adds EBUSY as a recognized success return. See the kernel commits for details: Kernel Git Commit 203702f, Kernel Git Commit 3301483, and Kernel Git Commit bcd7f1f.
Detection Methods for CVE-2026-97591
Indicators of Compromise
- No public indicators of compromise or in-the-wild exploitation have been reported for this vulnerability.
- Unexpected cryptographic operation failures or stalled HMAC requests on s390 systems may indicate exposure.
Detection Strategies
- Inventory Linux hosts running on IBM Z (s390) architecture and verify kernel versions against the fixed commits.
- Review kernel logs (dmesg, /var/log/messages) for crypto engine errors associated with PHMAC request submission.
- Use configuration management tooling to detect kernel builds that include the vulnerable PHMAC driver without the referenced patches.
Monitoring Recommendations
- Monitor kernel error rates and crypto subsystem telemetry on s390 workloads for anomalies.
- Track package and kernel update status across Linux fleets to confirm patch adoption.
- Alert on unexpected restarts or crypto-related kernel warnings on affected hosts.
How to Mitigate CVE-2026-97591
Immediate Actions Required
- Identify all IBM Z (s390) Linux systems in the environment and confirm whether they run a kernel including the PHMAC driver.
- Apply vendor-provided stable kernel updates incorporating the upstream fix.
- Validate cryptographic workloads post-patch to confirm correct HMAC operation on affected systems.
Patch Information
The fix adds EBUSY as a recognized successful transfer code in the PHMAC driver. It is included in the upstream Linux kernel through commits 203702f, 3301483, and bcd7f1f. Consume the fix via your Linux distribution's stable kernel update channel.
Workarounds
- No official workaround is documented; applying the upstream kernel patch is the recommended remediation.
- On non-s390 architectures, the PHMAC driver is not loaded, so those systems are not affected.
# Verify running kernel version on affected s390 hosts
uname -r
# Check installed kernel package status (example for RHEL/SLES)
rpm -qa | grep -E '^kernel-'
# Apply distribution kernel updates and reboot
sudo zypper update kernel-default # SLES on s390
sudo dnf update kernel # RHEL on s390
sudo reboot
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

