s390/crypto: Fix handling of EBUSY in PHMAC when req is pushed to crypto engine (CVE-2026-97591) | HOL Guard CVE

Unknown severity · Source severity not reportedCVE-2026-97591

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

Answer in brief

CVE-2026-97591 records a Unknown severity vulnerability in s390/crypto: Fix handling of EBUSY in PHMAC when req is pushed to crypto engine. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Sep 25, 2026Updated Sep 25, 2026Source checked Sep 25, 2026First seen by HOL Sep 25, 2026Material review Sep 25, 2026

Upstream Advisory

Key facts

Risk: Unknown severitySource severity not reported
Exploitation: Not marked as known exploited
Affected software: 2 mapped packages or products
Fix availability: Available

Why this deserves its current priority

A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
Linux/Linuxgeneric	>=cbbc675506cc4cd93e6f895e7c1f693156f9a95c <203702f0013f9b7324e8c5facb6cd6e9c0942b13 \|\| >=cbbc675506cc4cd93e6f895e7c1f693156f9a95c <bcd7f1f1e2f2882ad206f72425255be105178151 \|\| >=cbbc675506cc4cd93e6f895e7c1f693156f9a95c <330148371401de474b656eaf521861f12ec1a1ce	203702f0013f9b7324e8c5facb6cd6e9c0942b13, bcd7f1f1e2f2882ad206f72425255be105178151, 330148371401de474b656eaf521861f12ec1a1ce
Linux/Linuxgeneric	6.17	Not reported

Recommended response

Check inventory. Check lockfiles and deployed manifests for Linux/Linux, Linux/Linux.
Review the reported fix. Update Linux/Linux to 203702f0013f9b7324e8c5facb6cd6e9c0942b13 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

Published upstream
Sep 25, 2026
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Sep 25, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Sep 25, 2026

Sources and claim methodology

Upstream source 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.

Quoted source text, attributed separately from HOL analysis.