CVE-2026-97591

s390/crypto: Fix handling of EBUSY in PHMAC when req is pushed to crypto engine

N/A
Published: September 25, 2026 at 10:22 AM UTC
Updated: October 19, 2026 at 10:17 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

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

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

6.17cbbc675506cc4cd93e6f895e7c1f693156f9a95c
Vendor states this is fixed in 203702f0013f9b7324e8c5facb6cd6e9c0942b13 (fixed)
Vendor states this is fixed in 330148371401de474b656eaf521861f12ec1a1ce (fixed)
Vendor states this is fixed in bcd7f1f1e2f2882ad206f72425255be105178151 (fixed)
Vendor states this is fixed in 6.17 (unaffected)
Vendor states this is fixed in 6.18.53 (unaffected)
Vendor states this is fixed in 7.2.7 (unaffected)
Vendor states this is fixed in 7.3 (unaffected)
Vendor states this is fixed in 7.3-rc3 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card