Strix
64.7K

CVE-2026-97591

Unknown

Last modified

CVE-2026-97591 is a vulnerability of currently unknown severity. 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..

Description

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 Software

Source: CNA advisory (CVE.org). NVD analysis pending.

VendorProductVersions
LinuxLinux>= cbbc675506cc4cd93e6f895e7c1f693156f9a95c, < 203702f0013f9b7324e8c5facb6cd6e9c0942b13; >= cbbc675506cc4cd93e6f895e7c1f693156f9a95c, < bcd7f1f1e2f2882ad206f72425255be105178151; >= cbbc675506cc4cd93e6f895e7c1f693156f9a95c, < 330148371401de474b656eaf521861f12ec1a1ce
LinuxLinux6.17

References

Timeline

Published
Last Modified
Status
Received

Frequently Asked Questions

What is CVE-2026-97591?
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.
How severe is CVE-2026-97591?
Severity scoring for CVE-2026-97591 is pending analysis.
How do I fix CVE-2026-97591?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

How Strix Helps

Related CVEs from 2026

View all 2026CVEs →

Are you affected by CVE-2026-97591?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST